On Windows Server 2016 just type DNS in the search Box to quickly find the DNS console.
To verify the PTR record works open up Power Shell (command prompt will work also)nslookup followed by the IP you want to lookup.
You can see in the picture above the IP returned the hostname PC1.
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.
Now, type in the start of the subnet range of your network.
For this demo I’m setting up a zone for subnet 192.168.0.0/24. I recommend picking the first option “Allow only secure dynamic updates”That completes the wizard, click finish Back in the DNS console click on “Reverse Lookup Zone”I can now see the new zone listed. Now I’ll click the 0.168.192zone to view the reocrds So far I have only the SOA and NS resource records, no PTR records.
riginally posted this in 4/2006, and updated throughout the years, but I still get questions from time to time asking why updates are not working, especially PTR.
Well, I thought it’s time for an update and to just offer a summary in the beginning, because in this day and age, no one wants to read!
I’m creating a record for IP, 192.168.0.206 with the hostname of pc1.
Back in the DNS console I can see the PTR record listed.
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.