How to Create a Reverse Lookup DNS Zone in Windows Server 2003?

Reverse lookup zones in DNS servers of Windows server 2003 are used to resolve IP addresses to their respective FQDN names. This process works as the complement of forward Lookup zones where names are resolved to their respective IP addresses. Also PTR records are created when reverse lookup zones are configured and are helpful in many network scenarios. However reverse lookup zones are mostly used for testing purposes. When installed you can test reverse lookup zone by using ping command followed by the IP address and –a (for example: ping 192.168.0.24 –a). When this command is typed you get the reply from the Fully Qualified Domain Name (FQDN) of that IP address. You can configure reverse lookup zone by following the steps given below:

1. Log on to the DNS server using administrative privileges.
2. Click on Start button.
3. From the start menu go to Administrative Tools and from the submenu click on DNS.
4. From the opened snap in expand the name of your computer (which is PCTIPS-3000 in this case).
5. From the list right click on Reverse Lookup Zone and from the context menu click on New Zone.
6. On Welcome to the News on Wizard page click on Next button.
7. On Zone Type page make sure that Primary zone radio button is selected and click on Next button.
8. On Active Directory Zone Replication Scope page leave all the settings default and click on Next button.
9. On Reverse Lookup Zone Name page ensure that Network ID radio button is selected and type the network ID for which you want to create this reverse lookup zone. (192.168.0. In this case)
10. 
11. Once done click on Next button.
12. On Dynamic Updates page make sure that Allow only secure dynamic updates (recommended for Active Directory) radio button is selected and click on Next button.
13. On Completing the New Zone Wizard page view the summary and click on Finish button.

More Info:

When you create a reverse lookup zone you can automatically create the PTR records for this zone while creating Host (A) records. This process will reduce some administrative overhead.