We have split scope DHCP with the DHCP servers using a shared account to register DNS. However, the process is working extremely poorly because when a different DHCP server responds to DHCP lease requests, it fails to update the previous DNS record so the incorrect DNS record remains and it causes all kinds of problems. The most common issue is a user attempting to use Remote Desktop to access their workstation, but they cannot because DNS still has the wrong address.
I thought the shared credential was supposed to prevent this issue because in theory the most recently used DHCP server would update the DNS record as soon as it gave out a lease and overwrite the old record, but in practice this is not working.
We have DNS scavenging running, but it cannot keep up with the daily DNS changes.
When a user is unable to access their workstation by name, to fix this, we go into DNS and manually delete the old records from each DNS server and then go to the local workstation and register DNS manually by running the registerdns command. Then we have the user run flushdns on the system they are using to remotely access their workstation.
Within a few minutes, the issue is resolved, but is a waste of time and productivity for everyone to keep dealing with this.
What is the best way to clear this up? Should we stop DHCP servers from registering the clients DNS records and have the clients do it instead? That seems to make sense since the client always knows what the current IP address is and should keep DNS up to date. If so, how do we configure this?
If not, what is a better solution?