DNS reverse lookup records aren't getting updated from the DHCP server
We recently moved the DHCP server from an older Win 2000 box to a Win 2003 server. The move seemed to go fine and DHCP itself is working but think i may have missed something related to DNS. The DNS reverse lookup records do not seem to be being updated by the new DHCP server. When i checked DNS for a specific workstation and then connect to it remotely by both the listed pc name and IP I ended up at two different machines. I went into the DNSmgmt window in Admin tools, and it had at least half a dozen computers with that same IP listed. There was another computer on there that had 15-20 PTR files with different IPs listed. Any help with this would be greatly appreciated!
ASKER
Thanks, looks like the "Discard A and PTR records when lease is deleted" was already checked on the DHCP server. Can you give me more details on Scavenging? The DNS server is running on a Windows 2000 machine at present, though it too will be updated to 2003 in the near future. Did do the manual clean-up this morning but not sure if the problem will reappear over time yet or not.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ah, "Only Secure Updates" is set. Since I did the manual cleanup this morning, will i still need to set that to "yes" for the future or should it update normally from this point forward?
delete your reverse DNS zone, and then recreate it..
also run ipconfig /flushdns on the DNS box..
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Also this earlier question, now PAQ'd, contains a lot of detail about scavenging and DDNS:
https://www.experts-exchange.com/questions/22023097/Under-what-conditions-are-Dynamically-Registered-Records-Scavenged-from-Windows-2003-DNS.html
https://www.experts-exchange.com/questions/22023097/Under-what-conditions-are-Dynamically-Registered-Records-Scavenged-from-Windows-2003-DNS.html
It should update normally from now on, assuming there are no other issues.
ASKER
Thanks for all the help. Think Shift-3 ultimately had the solution in this case, but appreciate the advice on scavenging from feptias as well. Will split up the points a bit, but thank you both again.
Open the DHCP Management Console on the server, then right click on the node that has the name of your server and select Properties. Now look at the settings in the DNS tab. Try ticking the option "Discard A and PTR records when lease is deleted". You may also find it useful to enable scavenging in the DNS server - this will remove stale DNS records after a set period of time. You may have to manually delete some of the stale DNS records at first just to get things tidy. After that the automated processes should keep it clean. If you want more details about scavenging, just say.