RE: draft-ietf-dhc-dhcp-dns-02.txt

[Peter Ford <[e-mail]>]

A case where I can see the DHCP server updating the DNS is when the host
is unable to do so for itself.  One would imagine that these are old
hosts that in all likelihood do not implement
draft-ietf-dhc-dhcp-dns-02.txt.  In this case the DHCP server might have
some a priori knowledge of the name of the client and can update
accordingly as local policy warrants.

This leaves open what should be the default behavior of "new" clients
>and servers.  My sense is that there is not a lot of traction building
draft-ietf-dhc-dhcp-dns-02.txt into a client.  I would be interested in
hearing where people think draft-ietf-dhc-dhcp-dns-02.txt  is a
requirement.

Thanks in advance,

peter




>----------
>From: 	Yakov Rekhter[SMTP:[e-mail]]
>Sent: 	Sunday, November 03, 1996 12:10 PM
>To: 	Multiple recipients of list
>Subject: 	Re: draft-ietf-dhc-dhcp-dns-02.txt 
>
>Deke,
>
>> I'm trying to convince myself one way or the other that there is
>> provision for a DHCP client to specify a client FQDN option in the DHCP
>> transaction which is for a DNS zone other than the zone usually
>> associated with the address assigned by the DHCP server itself, and
>> that under the right circumstances that request can be honored.
>> 
>> For example, can I visit MIT and boot up my laptop using DHCP (talking
>> to some MIT DHCP server) to acquire the address but then specify a 
>> upenn.edu FQDN?
>
>Yes, you should be able to do this. However, if you would assume that
>the DHCP server (at MIT) would be responsible for updating not just
>the PTR RR (associated with the address), but your A RR
>(that is at upenn.edu), then you need to figure out a whole bunch
>of security/authentication-related issues. IMHO you'll be much
>better off if the DHCP server at MIT would just update the PTR RR,
>and the client (your laptop) would be responsible for updating
>its A RR.
>
>Yakov.
>