This article describes best practices for the configuration of Domain Name System (DNS) client settings in Windows 2000 Server and in Windows Server 2003. The recommendations in this article are for the installation of Windows 2000 Server or Windows Server 2003 environments where there is no previously defined DNS infrastructure.
Domain controller with DNS installed
On a domain controller that also acts as a DNS server, Microsoft recommends that you configure the domain controller's DNS client settings according to these specifications:
If the server is the first and only domain controller that you install in the domain, and the server runs DNS, configure the DNS client settings to point to that first server's IP address. For example, you must configure the DNS client settings to point to itself. Do not list any other DNS servers until you have another domain controller hosting DNS in that domain.
During the DCPromo process, you must configure additional domain controllers to point to another domain controller that is running DNS in their domain and site, and that hosts the namespace of the domain in which the new domain controller is installed. or if using a 3rd-party DNS to a DNS server that hosts the zone for that DC's Active Directory domain. Do not configure the domain controller to utilize its own DNS service for name resolution until you have verified that both inbound and outbound Active Directory replication is functioning and up to date. Failure to do so may result in DNS “Islands”. For more information on DNS Islands, please see “Chapter 2 – Structural Planning for Branch Office Environments” in the “Planning” section of the Windows 2000 Server Active Directory Branch Office Guide at the following Microsoft Web site:
For more information about a related topic, click the following article number to view the article in the Microsoft Knowledge Base:
275278 DNS Server becomes an island when a domain controller points to itself for the _msdcs.ForestDnsName domain
After you have verified that replication has completed successfully, DNS may be configured on each Domain Controller in either of two ways, depending on the requirements of the environment. The configuration options are:
Configure the Preferred DNS server in TCP/IP properties on each Domain Controller to use itself as Primary DNS Server.
Advantages: Ensures that DNS queries originating from the Domain Controller will be resolved locally if possible. Will minimize impact of Domain Controller’s DNS queries on the network
Disadvantages: Dependant on Active Directory replication to ensure that DNS zone is up to date. Lengthy replication failures may result in an incomplete set of entries in the zone.
Configure all Domain Controllers to use a centralized DNS server as their Preferred DNS Server.
Minimizes the reliance on Active Directory replication for DNS zone updates of Domain Controller locator records. This includes faster discovery of new or updated Domain Controller locator records, as replication lag time is not an issue.
Provides a single authoritative DNS server, which may be useful when troubleshooting Active Directory replication issues
Will more heavily utilize the network to resolve DNS queries originating from the Domain Controller
DNS name resolution may be dependant on network stability; loss of connectivity to the Preferred DNS server will result in failure to resolve DNS queries from the Domain Controller. This may result in apparent loss of connectivity, even to locations that are not across the lost network segment.
A combination of the two strategies is possible, with the remote DNS server set as Preferred DNS server, and the local Domain Controller set as Alternate (or vice versa). While this strategy has many advantages, there are factors that should be considered before making this configuration change:
The DNS client does not utilize each of the DNS servers listed in TCP/IP configuration for each query. By default, on startup the DNS client will attempt to utilize the server in the Preferred DNS server entry. If this server fails to respond for any reason, the DNS client will switch to the server listed in the alternate DNS server entry. The DNS client will continue to use this alternate DNS server until:
It fails to respond to a DNS query, or:
The ServerPriorityTimeLimit value is reached (15 minutes by default). For more information, click the following article number to view the article in the Microsoft Knowledge Base:
286834 The DNS Client service does not revert to using the first server in the list
Please note, only a failure to respond will cause the DNS client to switch Preferred DNS servers; receiving an authoritative but incorrect response does not cause the DNS client to try another server. As a result, configuring a Domain Controller with itself and another DNS server as Preferred and Alternate servers helps to ensure that a response is received, but it does not guarantee accuracy of that response. DNS record update failures on either of the servers may result in an inconsistent name resolution experience.
Do not configure the DNS client settings on the domain controllers to point to your Internet Service Provider's (ISP's) DNS servers. If you configure the DNS client settings to point to your ISP's DNS servers, the Netlogon service on the domain controllers does not register the correct records for the Active Directory directory service. With these records, other domain controllers and computers can find Active Directory-related information. The domain controller must register its records with its own DNS server.
To forward external DNS requests, add the ISP's DNS servers as DNS forwarders in the DNS management console. If you do not configure forwarders, use the default root hints servers. In both cases, if you want the internal DNS server to forward to an Internet DNS server, you also must delete the root "." (also known as "dot") zone in the DNS management console in the Forward Lookup Zones folder.
For more information about how to remove the root zone, click the following article number to view the article in the Microsoft Knowledge Base:
If the domain controller that hosts DNS has several network adapters installed, you must disable one adapter for DNS name registration.
For more information about how to configure DNS correctly in this situation, click the following article number to view the article in the Microsoft Knowledge Base:
292822 Name resolution and connectivity issues on a Routing and Remote Access Server that also runs DNS or WINS
To verify your domain controller's DNS client settings, type the following command at a command prompt to view the details of your Internet Protocol (IP) configuration:
To modify the domain controller's DNS client configuration, follow these steps:
Right-click My Network Places, and then click Properties.
Right-click Local Area Connection, and then click Properties.
Click Internet Protocol (TCP/IP), and then click Properties.
Click Advanced, and then click the DNS tab. To configure the DNS information, follow these steps:
In the DNS server addresses, in order of use box, add the recommended DNS server addresses.
If the For resolution of unqualified names setting is set to Append these DNS suffixes (in order), Microsoft recommends that you list the Active Directory DNS domain name first (at the top).
Verify that the DNS Suffix for this connection setting is the same as the Active Directory domain name.
Verify that the Register this connection's addresses in DNS check box is selected.
Click OK three times.
If you change any DNS client settings, you must clear the DNS resolver cache and register the DNS resource records. To clear the DNS resolver cache, type the following command at a command prompt:
To register the DNS resource records, type the following command at a command prompt:
To confirm that the DNS records are correct in the DNS database, start the DNS management console. There should be a host record for the computer name. (This host record is an "A" record in Advanced view.) There also should be a Start of Authority (SOA) record and a Name Server (NS) record that points to the domain controller.
Domain controller without DNS installed
If you do not use Active Directory-integrated DNS, and you have domain controllers that do not have DNS installed, Microsoft recommends that you configure the DNS client settings according to these specifications:
Configure the DNS client settings on the domain controller to point to a DNS server that is authoritative for the zone that corresponds to the domain where the computer is a member. A local primary and secondary DNS server is preferred because of Wide Area Network (WAN) traffic considerations.
If there is no local DNS server available, point to a DNS server that is reachable by a reliable WAN link. (Up-time and bandwidth determine reliability.)
Do not configure the DNS client settings on the domain controllers to point to your ISP's DNS servers. Instead, the internal DNS server should forward to the ISP's DNS servers to resolve external names.
Windows 2000 Server and Windows Server 2003 member servers
On Windows 2000 Server and Windows Server 2003 member servers, Microsoft recommends that you configure the DNS client settings according to these specifications:
Configure the primary and secondary DNS client settings to point to local primary and secondary DNS servers (if local DNS servers are available) that host the DNS zone for the computer's Active Directory domain.
If there are no local DNS servers available, point to a DNS server for that computer's Active Directory domain that can be reached through a reliable WAN link (Up-time and bandwidth determine reliability.)
Do not configure the client DNS settings to point to your ISP's DNS servers. If you do so, you may experience issues when you try to join the Windows 2000-based or Windows Server 2003-based server to the domain, or when you try to log on to the domain from that computer. Instead, the internal DNS server should forward to the ISP's DNS servers to resolve external names.
Windows 2000 Server and Windows Server 2003 non-member servers
If you have servers that are not configured to be part of the domain, you can still configure them to use Active Directory-integrated DNS servers as their primary and secondary DNS servers. If you have non-member servers in your environment that use Active Directory-integrated DNS, they do not dynamically register their DNS records to a zone that is configured to accept only secure updates.
If you do not use Active Directory-integrated DNS, and you want to configure the non-member servers for both internal and external DNS resolution, configure the DNS client settings to point to an internal DNS server that forwards to the Internet.
If only Internet DNS name resolution is required, you can configure the DNS client settings on the non-member servers to point to the ISP's DNS servers.
For more information about Windows 2000 DNS and Windows Server 2003 DNS, click the following article number to view the article in the Microsoft Knowledge Base:
291382 Frequently asked questions about Windows 2000 DNS and Windows Server 2003 DNS
For more information about DNS client-side name resolution, click the following article number to view the article in the Microsoft Knowledge Base:
325509 Support WebCast: Windows 2000 client-side name resolution