JH>>> I'm guessing everyone is set already as far as dyndns-handling JH>>> is concerned? TDP>> I wonder why you want to re-invent the wheel?
MR> Possibly he's already running his own nameservers anyway. Then DynDNS MR> would be be just a simple configuration change for his named (bind). MR> And he doesn't have to worry about free services changing to paid MR> subscription suddenly.
That might be a good reason indeed, if it's for his own use. But making it public so that others can use it as well seems like quite a lot of work for something that already exists.
