dynamic dns update

Jason Schoon floydpink at gmail.com
Tue Jul 25 15:28:14 UTC 2006


On 7/25/06, Paul Fox <pgf at brightstareng.com> wrote:
>
> jason wrote:
> > On 7/24/06, Paul Fox <pgf at brightstareng.com> wrote:
>
> > This option is currently hardcoded to have the server do the
> > actual update.  If you wanted the client to do it instead, you
> > would have to modify that code and add the mechanism to
> > update.
>
> wouldn't that also require some sort of secure DNS connection?  but
> PCs do this, right?  how do they authenticate?


It does require a secure connection for update.  RFC 2136 describes it I
believe.  I don't think PC's generally do this.  Windows has the option to
update DNS records, but if I remember right that just tells their DHCP
client to behave just as udhcpc does with the -F flag.

> There are IETF drafts and/or RFC's discussing how the DHCP to
> > DNS update should occur.  I have never written this code
> > myself, as I have always been concerned with the client side,
> > and the servers I worked with always supported it already.
>
> most of my experience is with the server side, because i worked
> for a while on a server that was an early implementer of the
> protocol.  but as i recall, in that case it was completely
> server-to-server -- the client had no control of its own
> hostname.  (it was for large enterprise and cable-scale networks.)
>
> paul
> =---------------------
> paul fox, pgf at brightstareng.com
> _______________________________________________
> busybox mailing list
> busybox at busybox.net
> http://busybox.net/cgi-bin/mailman/listinfo/busybox
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.busybox.net/pipermail/busybox/attachments/20060725/24c29a49/attachment-0001.htm 


More information about the busybox mailing list