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

Yakov Rekhter <yakov@cisco.com> Sun, 03 November 1996 20:18 UTC

Received: from cnri by ietf.org id aa05004; 3 Nov 96 15:18 EST
Received: from marge.bucknell.edu by CNRI.Reston.VA.US id aa14463; 3 Nov 96 15:18 EST
Received: from reef.bucknell.edu by mail.bucknell.edu; (5.65v3.2/1.1.8.2/17Jul96-0109PM) id AA19114; Sun, 3 Nov 1996 15:11:21 -0500
Date: Sun, 3 Nov 1996 15:11:21 -0500
Message-Id: <199611031930.LAA11974@hubbub.cisco.com>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: Yakov Rekhter <yakov@cisco.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Re: draft-ietf-dhc-dhcp-dns-02.txt
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4

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.