Dynamic DNS

[Irina Goble]

Barr,

> 
> 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.
> 
	It is just logical to do dynamic DNS updates for dynamic IP addresses
and have static IP - domain name mappings for static IP addresses.

> 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.
> 
	If it is possible to separate these docking stations in a group 
with a special domain for this group, on a DNS server allow dynamic DNS
updates for this zone. Then it can work with a patch (sorry, it is rough)
I sent last week to Ted and Brian, when the DHCP server can keep a status
of updates and will stop sending update requests if DNS server rejects 
them.

> 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
>