Dynamic dns records not updating
When a new client gets an IP address, DHCP doesn't update DNS with the record. The DHCP and DNS are on the same box (which is also the primary DC).
I have checked the event viewer logs for the DHCP and DNS server but nothing is present?
That doesn't exactly seem to be the case from your experience, but might be close.... Massimo, are you able to pull a wireshark trace and check the DHCPREQUEST Packet?
There should be a flag set to "1" if the client is supposed to update both the A record and PTR record.
I've stumbled upon a strange behaviour with Windows machines, which seems to be fairly consistent between all Windows versions from Vista/2008 to 8.1/2012 R2; it doesn't happen instead when using Windows XP or Windows Server 2003.
The problem is this: when the network adapter is configured for DHCP and the DHCP server doesn't register DNS records on behalf of its clients (because it can't, or because it's not configured to do so), then A friend not on SF said: "That's normal, PTR is only updated by DHCP in Win2K+".
in the TCP/IP settings of the network interface: As much as it may appear strange, this is the only solution to ensure Windows will register both the A and the PTR records for a DHCP network connection; otherwise, it will only register the A record. 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.
And make sure the DNS dynamic update credentials are correct and appropriate permissions are applied for this to work As I said in the question, configuring the DHCP server is not an option. It won't register DNS records for its clients, period.
They should be able to handle it, since all of them are domain members.