I don't have a convenient test environment to try it...In Windows 2008 and above, there is an option in the DHCP scope to set up the DHCP server to automatically update the authoritative DNS servers with the host (A) and PTR) records of the DHCP clients.We have a network with a segment for client machines that uses a couple of Windows 2008 R2 servers for DNS and DHCP (all AD-integrated).Clients are mostly Windows 7 machines with a few XP and Vista.The way we solve this is by manually deleting the offending records and issue "ipconfig /registerdns" on the client.
This could easily be overkill, but since the above answers didn't cover things from a group policy angle here goes. sends option 81 and its fully qualified domain name to the DHCP server and requests the DHCP server to register a pointer resource record (PTR RR) on its behalf.
Issuing the ipconfig /registerdns also appears to correct the symptoms in our case as well. If so, please share No, we never figured out the issue.
It got better when we switched our DCs to 2012 server but didn't go away.
Since we're a small network, we've decided to live with the issue rather than invest a lot of time to investigate.
Running DNS on two 2008 R2 Servers setup as AD integrated for both Forward and all Reverse zones. In DNS the following was set: -Type AD Integrated -Replication All domain controllers in this domain -Dynamic Updates None (why that was like that who knows) -Scavenging is not in use yet I changed Dynamic updating to Secure and Non Secure since I was not sure how it would affect all the non windows servers currently in there.
The DHCP server likely won't have permissions unless you've manually set that up in your environment, and no other client will ever be able to register that address until it's manually deleted at some point.