Reverse search zones are used to resolve IP addresses to a hostname. For reverse search zones to work they use a PTR phonograph record that provides the map of the IP address in the zone to the hostname .
For model, I can look up the IP 10.1.2.88 and see that it resolves to the hostname “ nodaway ”. Without a reverse search zone and PTR record, I would not be able to do this .
- Do You Really Need Reverse Lookup Zones and PTR Records?
- How to Configure Reverse Lookup Zones on Windows Server 2016
- Verify Reverse Lookup Zone
- How to Create PTR Records
- How to Verify PTR Record Is Working
Do You Really Need Reverse Lookup Zones and PTR Records?
Every network is different so it depends. Unless you host your own electronic mail waiter or have an application that requires it may not be required .
even if you don ’ thyroxine have requirements for them I still recommend setting them up because they are highly helpful when troubleshooting. You can read more about this in my DNS Best Practices guide .
How to Configure Reverse Lookup Zones on Windows Server 2016
These steps are very exchangeable across other all waiter versions server versions ( 2008, 2012 ) .
Step 1: Open the DNS Management Console
On Windows Server 2016 just type DNS in the search Box to cursorily find the DNS comfort .
Step 2: Create New Reverse Lookup Zone
In the DNS cabinet good click on “ Reverse Lookup Zones ” and Select “ New Zone ”
This will start the modern zone charming .
Step 3: Choose Zone Type (New Zone Wizard)
On the Zone Type page blue-ribbon Primary zone
Choose to replicate to all DNS servers running on knowledge domain controllers in this domain .
Choose IPv4 or IPv6, for this show I ’ megabyte setting up IPv4 .
now, type in the starting signal of the subnet scope of your net .
For this demonstration I ’ molarity setting up a zone for subnet 192.168.0.0/24 .
Choose active update option .
I recommend picking the beginning option “ Allow only secure dynamic updates ”
That completes the ace, suction stop finish
Verify Reverse Lookup Zone
back in the DNS cabinet cluck on “ Reverse Lookup Zone ”
I can now see the fresh zone listed. The subnet will display backwards that is normal .
immediately I ’ ll click the 0.168.192.in.addr.arpa zone to view the reocrds
so army for the liberation of rwanda I have only the SOA and NS resource records, no PTR records .
once clients start dynamically updating their DNS the PTR records should start populating. You can besides manually produce PTR records for systems that are not configured to dynamically update .
How to Create PTR Records
Lets walk through manually creating a PTR record. This is only needed if a system is not configured to dynamically update. This may be the case for systems with static IP addresses like servers .
right click the zone and select “ New Pointer ( PTR ) ”
Enter the Host IP Address and Host name fields and click OK .
I ’ molarity creating a record for IP, 192.168.0.206 with the hostname of pc1 .
rear in the DNS console I can see the PTR record listed .
How to Verify PTR Record Is Working
To verify the PTR record works open up PowerShell ( command prompt will work besides ) .
type nslookup followed by the IP you want to lookup .
Read more: Apollo for Reddit
You can see in the visualize above the IP returned the hostname PC1 .
That is all there is to it .
Pretty easy correct ?