Also, PTR resource records must exist for all the computers in your network.For more information about adding a reverse lookup zone, see "Adding a Reverse Lookup Zone" earlier in this chapter.If the server does not support dynamic update, you need to add these records manually.The Netlogon service creates a log file that contains all the locator resource records and places the log file in the following location: % %\System32\Config\You can check this file to find out which locator resource records are created for the domain controller.Next, query for the SOA record by typing the following and pressing ENTER: If your server is configured correctly, you see an SOA record.
Make sure that the authoritative name server listed in the NS record can be contacted to request queries by typing the following: server Next, query the server for any name for which it is authoritative.
However, you need them if you want clients to be able to resolve FQDNs from IP addresses.
Also, PTR resource records are commonly used by some applications for security purposes, to verify the identity of the client.
On a semi related note: I know this has been a touchy subject some places I have looked. For each DC, what should their local DNS settings be?
If you use a third-party DNS server to support Active Directory, you must perform configuration tasks manually, and doing so, you might cause common configuration errors that prevent DNS and Active Directory from working properly.