Reverse lookup zone in dns is not updating
A flag of "0" means the client updates the A record and requests that the server update the PTR record on its behalf. Also in the DHCP scope make sure == Click the DNS tab, click Properties, and then click to select the Dynamically update DNS A and PTR records only if requested by the DHCP clients check box == is set.
They should be able to handle it, since all of them are domain members.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+".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.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.
The dynamic update client registers an address resource record (A RR). the DHCP server can be configured to instruct the client to allow the server to register both records with the DNS.
Statically configured (non-DHCP) clients register both the A RR and the PTR RR with the DNS server themselves.
Edit: According to the article linked by The Cleaner below, the GPO I mentioned in my comment will not do what you want (yeah MS and closed-source software).
But checking the boxes for "Register this connection's address in DNS" and "Use this connection's DNS suffix in DNS registration" makes it work.
I don't have a convenient test environment to try it...
The GPO doesn't change anything, but enabling "Use this connection's DNS suffix in DNS registration" actually did the trick.