It is an issue on Server 2000, 2003, 2008, 2008R2, Server 2012, Server 2012 R2 and will likely be an issue in the newer builds.
If you check your servers event viewer you will see EVENT ID 1056: The DHCP service has detected that it is running on a DC and has no credentials configured for use with Dynamic DNS registrations initiated by the DHCP service. Credentials for Dynamic DNS registrations may be configured using the command line “netsh dhcp server set dnscredentials” or via the DHCP Administrative tool.
I mentioned this and got 'Yeah, we know.'So I decided to do some poking around.
When I joined the company, I noted that a lot of name lookups were failing or pointing at the wrong machines.
If you want more information you may find the following useful:
You, as a DHCP administrator, might want to enable DNS integration in order to automatically update the DNS records dynamically with the DHCP client computers’ information whenever the DHCP server assigns the IP address and other settings to them.
The Dns Update Proxy group, despite its description, had a domain admin account and the BES Service Account as members.
I did a bit of reading and discovered that the group should have DNS computer accounts in, if the zones are configured to only be updated securely - which they were. I am forever getting incorrect / outdated lookups when connecting to machines.