Dynamic DNS

[HIBBS, BARR (PB)]

Irina--

sorry if I wasn't clear.  What I was trying to say is that certain static
hosts should be able to be configured to have the DHCP server perform
dynamic DNS updates on their behalf, while others should not.

I basically have two types of static hosts:  the truly static client
workstation which for various reasons must have a static IP address (and an
invariant forward and reverse address mapping in DNS), and docking stations,
which are assigned a static address, but the forward and reverse mappings
between IP address and fully-qualified domain name are *not* invariant.

Of course, nothing prevents the server from performing dynamic updates
unless there is a programmatic or policy restriction against it -- but I
currently support over 21,000 static assignments and nearly 118,000 dynamic
addresses.  I'd just as soon never perform dynamic updates of DNS for the
truly static client:  only for the hotel docking stations, of which I have
about 600.

Reducing traffic on my intranet is a significant issue for me:  my DHCP
servers currently process between 4 and 7 messages per second, 24x7, so I
look for anything that will mitigate the server load.

--Barr





> From: 	Irina Goble[SMTP:irinag at ims.com]
> Sent: 	Friday, August 06, 1999 1:19 PM
> To: 	dhcp-hackers at isc.org
> Subject: 	RE: Dynamic DNS
> 
> > 					 Ideally, hotel docking stations
> > would perform dynamic DNS update even though their IP address
> assignments
> > are static.
> > 
> 	What do you mean by that? What stops you from using dynamic
> addresses
> in this case?
>