dynamic dns update
Paul Fox
pgf at brightstareng.com
Tue Jul 25 12:05:49 UTC 2006
jason wrote:
> On 7/24/06, Paul Fox <pgf at brightstareng.com> wrote:
> >
> > step #3 can be done either by the client or by the DHCP server.
> > (well, some DHCP servers can do it. probably not all.)
> >
> > in any case, the busybox DHCP client can't currently do this.
>
>
> The busybox client does have the necessary option to tell the
> server to do this. It is (currently) undocumented in the
> usage, but if you specify a -F <domain name> the client will
> pass the information to the server and tell it to an update.
well, looky there. you're absolutely right. thanks. i didn't
realize we had that.
> 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?
> 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
More information about the busybox
mailing list