Our biggest issue with DHCP and DNS currently is that we are constantly re-imaging old systems, renaming systems, and rolling out new systems. These actions cause DHCP and DNS to not jive like we want them to. I have been beating my head against the desk trying to figure out a solution that will fit how we operate or only require minimal change in our current flow of operations. I am hoping someone else has some input on this issue.
We have our DHCP setup so that it currently does not manage DNS. It was updating DNS, but this was not fitting our flow and DNS Reverse Lookup was becoming a mess. We would have several entries for a single system name or a single IP in reverse lookup which would impact some of the local applications. To resolve this, we tried disabling the link between DHCP and DNS and are letting the PC's register with DNS on their own. DNS has never looked cleaner, expect for two problems. One is when we change the name of a system, it registers the new system with the same IP as it originally had. So DNS has 1 IP with 2 entries attached to it, the old name and the new name. The second issue is when we replace a system with new hardware. The name stays the same, but the IP changes due to the new hardware. In this case, DNS has 2 entries for the same name but different IP's.
We do have scavenging enabled and it cleans up the older entries. What we need is an instant cleansing/purge of the old records. I am at a loss as to the best way to resolve this. I have pursued numerous avenues, but am coming up dry.