Reverse DNS records not registered when using DHCP
Solution 1:
The solution is checking Use this connection's DNS suffix in DNS registration 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.
Solution 2:
I ran into the same issue years ago the following group policy settings are how I resolved it. This could easily be overkill, but since the above answers didn't cover things from a group policy angle here goes.
Computer Configuration\Administrative Templates\Network\DNS Client
- Connection Specific DNS Suffix: enabled, and set to mydomain.org
- Register DNS records with connection-specific DNS suffix: enabled
- Register PTR Records: enabled
- Dynamic Update: enabled
Solution 3:
According to MS:
Windows 2000 .. 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.
The article also mentions Changing registry entries changes the behavior of the dynamic update DNS client. So there might be a registry workaround... Looking
Edit:
According to the article linked by TheCleaner 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...