DNS Mess - How Would You Clean Up?

Running Win2K3 SP2 Servers with AD-integrated DNS.

All client machines are either Windows 2000 SP4 or Windows XP Pro.

All client machines have a checkbox under advanced IP properties to
"register this connection's address in DNS."

We are having a problem where our host records in DNS are not getting
cleaned up. This means I am getting entries such as:

RetiredMachine1 10.1.1.1
RetiredMachine2 10.1.1.1
CurrentMachine 10.1.1.1

This is not causing a problem for the current machine -- its ip address
really is 10.1.1.1 and it is the only machine using that ip address on the
network. However, this is causing some problems for a lot of my management
apps (WSUS, SolarWinds, etc.). Anyway, I need to get it cleaned up, but
I'm not sure how. I'm a little bit afraid to turn on scavenging for fear
that my servers -- who have static IPs but registered dynamically with
DNS -- might get deleted.

Any suggestions on the best and easiest way to get my DNS house in order?

All client machines are set to get IP addresses from DHCP servers.

DHCP servers are set to:

* Enable DNS dynamic updates according to settings below
* Dynamicall update DNS A and PTR records only if requested by DHCP
clients

* Discard A and PTR records when lease is deleted

(Option 15 is correctly configured in DHCP, and DHCP has an account
configured with the correct permissions to modify DNS).

Like I say, for some reason, it appears that A records are not getting
discarded. I
have a ton of duplicate IP addresses in my DNS pointing to machine names
that no longer exist.

Should I simply manually delete every A record for the workstations and let
them re-register themselves. (When do they register themselves, by the
way -- on boot? on DHCP lease?)

Or should I try to turn on scavenging?

Thank you.


.

Relevant Pages

  • Re: Dynamic DNS, DNS Records & Scavenging
    ... There are two DHCP ... Both the servers are set to update A and PTR records for clients. ... DNS however this doesn't seem to be the case. ... DNSUpdateProxy and when i did this i saw my test laptop register its ...
    (microsoft.public.windows.server.dns)
  • Re: networking private and public hosts questions
    ... DHCP isn't going to "help". ... you need to run NAT. ... Move all the Servers to the private side of the Firewall and start ... Controllers must point to themselves in thier DNS Setting and the ISP's DNS ...
    (microsoft.public.win2000.networking)
  • Re: Need DNS For Dummies! Please help!
    ... I set up DNS and DHCP on my Win2k Server without any ... > The FW/R is connected to the hub as are both of my servers. ... member servers and clients) MUST always and ONLY use ...
    (microsoft.public.windows.server.dns)
  • Re: DHCP assinged DNS servers dont work
    ... Although the WinXP firewall is enabled and configured via Group ... The first two DNS servers are AD controllers running ONLY core ... I have 75 WinXP machines on a Win2K3 domain using DHCP for address ...
    (microsoft.public.windows.server.networking)
  • Re: Troubleshooting connection loss (continued)
    ... "service network restart" clears the routing table and then hangs. ... DNS must be working even if the servers aren't from Verizon. ... that was to tell me if dhcp gave you an address or you were realy ...
    (comp.os.linux.networking)