Home        Tutorials        About        Services        Contact                        

 DNS 02 - Reverse Lookup Zones. First Pointer (PTR) Record. Testing DNS.¬†DiagramRecord. Diagram

01   02   03   04   05   06   07   08   09   10   11   12   13   14   15   16   17   18   19   20
                      Official PayPal Seal

Any donations are welcomed and appreciated! (100% Safe)

   $1    $5    $10   $Other



Feel free to click on the "Donate" button to donate
whatever you feel you can.

Tutorial Overview
Creating reverse lookup zones and zone type (standard primary)
Domain Name System (DNS) servers can enable clients to determine the DNS name of a host based on the host's IP address by providing a special zone called a reverse lookup zone. A reverse lookup zone contains pointer (PTR) resource records that map IP addresses to the host name. Some applications, such as secure Web applications, rely on reverse lookups. . Standard primary zone is the only zone type that can be edited or updated because the data in the zone is the original source of the data for all domains in the zone.

Creating the first pointer (PTR) record for the first DNS server
A PTR (Pointer) record is stored in a reverse lookup zone created on a DNS server. PTR records map known TCP/IP addresses to computer names. When a program knows the TCP/IP address of a computer and needs to find the host name of the computer, the program requests a reverse DNS lookup. The DNS server scans the list of PTR records in its reverse lookup zone for a record that maps to the TCP/IP address and returns the host name mapping to that address in the PTR record, to the requesting program.

Testing the first DNS server by running a (simple query)
Windows Server 2008 R2 has built-in functionality for monitoring a DNS server. Monitoring is useful to ensure that DNS resolution is configured properly. You can configure monitoring to occur manually or automatically. In order for the DNS server to do recursion properly, it first needs some helpful contact information about other DNS servers in the DNS domain namespace. if you're actively troubleshooting a DNS problem, you might want to configure testing to occur every 10‚Äď15 seconds. This interval will provide a rapid succession of test results. If you're monitoring DNS for problems as part of your daily administrative duties, you'll want a longer time interval, such as two or three hours.