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