I had to shut down my entire network to replace a bad fiber optic switch. Doing so meant that all of the Win XP PCs had to shut down as well to renegotiate a DHCP lease.

However, when they rebooted, quite a few of the PCs didn't get the same IP address (no big deal) but the DNS server added a new "A" record with their hostname. Now whenever I go to ping the PC by using the host name, I get multiple IP addresses. Obviously this won't work.

Is there a way to tell NAMED/DHCPSRVR to 'purge' the old (read: incorrect) DNS "A" records? I don't really want to go and delete the hundred or so objects in eDir.

Will/when will the old information expire?


Here is a snippit of a 'dig' that I did against the netware server:

american3.xtek.com. 0 IN A 192.168.202.68
american3.xtek.com. 0 IN A 192.168.202.80
american3.xtek.com. 0 IN A 192.168.202.119
american3.xtek.com. 0 IN A 192.168.202.123
american3.xtek.com. 0 IN A 192.168.202.129
ANNO.xtek.com. 0 IN A 192.168.202.109
ANNO.xtek.com. 0 IN A 192.168.202.119
appsrvx.xtek.com. 900 IN A 192.168.202.155
ASALACH.xtek.com. 0 IN A 192.168.202.74
ASALACH.xtek.com. 0 IN A 192.168.202.85
ASALACH.xtek.com. 0 IN A 192.168.202.119
ASALACH.xtek.com. 0 IN A 192.168.202.129
ASCHWAR.xtek.com. 0 IN A 192.168.202.123
ASCHWAR.xtek.com. 0 IN A 192.168.202.130
ASCHWAR.xtek.com. 0 IN A 192.168.202.135
atlantis.xtek.com. 900 IN A 192.168.202.60

Notice, that I have multiple entries so every time I 'ping american3.xtek.com' I get a different IP address.

This isn't such a big deal, except I have a Unix system running X windows that does a reverse lookup on the hostname. Unfortunately, 1/n times, it resolves to the wrong IP address and will not allow any X connections.

TIA,

Brian