Recurring addition to AD DNS in win2k

Running a domain with win 2003 servers and AD intergrated DNS.
We upgraded from the previous versions of the server product.

We recently noticed that a server that has not existed for years is showing up in the DNS entries! It is not assigning a pointer, but the host name and IP are correct for what the server used to be.

We tried assigning another device to that IP and creating the PTR. We also tried to delete the entry, but it keeps coming back and propogating to the remaining servers.

I have done a search for the source, and can confirm that it is not in WINS, there is not remaining account for the box, etc. The only theory that I have is that there is something in AD that keeps adding it back in.

Anyone have any ideas?

There's a reason why GUI's scare me...

Let's nip this guy at the source. where does Microsoft DNS Server store it's zone information? zone files? registry? database files? Find out, and remove it "manually".

It is unfortunate I am not familiar with Microsoft solutions to DNS configurations, but I'll help as best as I may since your topic seems to be disappearing down the list. ;-)

Was this 2003 domain upgraded from NT4 or W2k?

If from W2k, was the server a DC in the domain?

I believe this info is stored in the AD schema.

If it was a members server in a W2k domain, look in the computer object in 'active directories users and computers'. Is that machine listed in there?

If it was a DC in a W2k domain, there is a different procedure that is done through the command prompt. Here is a pdf of that procedure.

Could be an issue related to the upgrade. E.G. If the reocrd was not set as AD integraded in your old setup and the upgrade for some reason grabbed this zone and set as AD integrated.
I would download the DNS WMI Provider from microsoft.

DO NOT INSTALL THE DNS PROVIDER ON SERVER 2003 JUST USE THE FILE DNSZONES.VBS FROM THIS DISTRIBUTION.

Use the file dnszones.vbs to remove the zone from all your servers one at a time. This will most likely fail on all servers except for the one that has the zone set as standard primary and AD integrated. E.G. if one server has a screwed up config for this zone and it is set as AD intergrated then a standard remove of the domain will not remove the zone and in turn it is again propogated to all servers via AD.