Dynamic Host DNS Registration

Mark Andrews Mark_Andrews at isc.org
Fri Jul 8 11:50:40 UTC 2005


> On 7/8/05, Auer, Karl James <karl.auer at id.ethz.ch> wrote:
> > > The DHCP specification discusses the communication between the DHCP=3D2=
> 0
> > > client and server.  I don't think it says anything about DHCP servers=
> =3D20
> > > updating DNS servers.  That's something many DHCP servers do,=3D20
> > > but it's an add-on for integration, not part of the DHCP protocol.
> >=20
> > There are separate standards (still developing, I believe) covering
> > exactly *how* to update DNS entries dynamically, don't have the numbers
> > to hand.=20
> 
> Slightly offtopic for this list, but anyway:=20
> 
> The FQDN assignment (in the DHCP protocol) is done using DHCP Option
> 81 (client FQDN) AFAIR; it's specified in the draft mentioned below.
> 
> On the other hand, the DHCP-DNS interaction is specified in an ietf draft:=
> =20
> http://www.ietf.org/proceedings/00jul/I-D/dhc-dhcp-dns-12.txt
> 
> However, I'm not sure who implements that DHC ID RR yet - I don't
> think BIND does yet.

	As far as the nameserver is concern it is a opaque blob of
	data.  All current version of BIND will handle it.
 
> So, in order to support dynamic DNS updates, that router would have to
> support option 81, too. DHCP servers are supposed to support a minimum
> subset of options, but AFAIR this one isn't one of them.
> 
> 
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews at isc.org



More information about the bind-users mailing list