On Tue, 5 Jul 2005 at 15:56 -0600, Mitch Anderson wrote: > Hans Fugal wrote: > > >Ah yes, the confusion of terminology rears its head again. There's DDNS > >and there's DDNS. One is dyndns.com and friends, and one is RFC 2136. It > >looks like the proper name for RFC 2136 DDNS is not DDNS at all but > >"Dynamic Update." > > > > > Maybe I'm missunderstanding how dyndns.com and friends work, but arn't > they relatively the same thing(with DHCP out of the picture, for obvious > reasons)? The difference being dyndns.com(and friends) can't fully work > like the RFC because they don't have control over everyones DHCP > server. You just run a client side application which allows you to > authenticate and update their DNS servers(which may or may not use the > methods described in RFC2136)?
The idea is the same, yes. The difference is how the update is done - per RFC 2136 (which is usually dhcp server side) or with some other client that runs e.g. in a cron job on the client side. -- .O. Hans Fugal | De gustibus non disputandum est. ..O http://hans.fugal.net | Debian, vim, mutt, ruby, text, gpg OOO | WindowMaker, gaim, UTF-8, RISC, JS Bach --------------------------------------------------------------------- GnuPG Fingerprint: 6940 87C5 6610 567F 1E95 CB5E FC98 E8CD E0AA D460
signature.asc
Description: Digital signature
.===================================. | This has been a P.L.U.G. mailing. | | Don't Fear the Penguin. | | IRC: #utah at irc.freenode.net | `==================================='
