Verify DNS Server Recursive Name Resolution on the First Forest Root Domain Controller

  • Article

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

DNS server recursive name resolution is configured automatically during the Active Directory installation process, as described in "Install Active Directory on the Second Domain Controller" earlier in this chapter. If your design specifies a different configuration, you can use the DNS snap-in or Dnscmd.exe to modify these settings.

To verify DNS server recursive name resolution on the first forest root domain controller

  • Use the DNS snap-in to verify DNS server recursive name resolution for the method used in your organization based on the information in Table 6.2.

    Table 6.2   Information to Verify DNS Server Recursive Name Resolution

    Method Configuration

    Recursive name resolution by root hints

    Root hints are the recommended method to use for recursive name resolution in a Windows Server 2003 environment.

    No additional configuration is necessary. When the DNS server specified as the Preferred DNS server during the installation process is properly configured, the root hints are automatically configured. To verify the root hints by using the DNS snap-in:

    In the console tree, right-click the domain controller name, and then click Properties.

    In the Properties sheet for the domain controller, view the root hints on the Root Hints tab.

    Recursive name resolution by forwarding

    Only use Forwarders if that is what your organization’s design specifies. Root hints are the recommended method to use for recursive name resolution in a Windows Server 2003 environment.

    Forward unresolved queries to specified DNS servers. To verify forwarding by using the DNS snap-in:

    In the console tree, right-click the domain controller name, and then click Properties.

    On the Forwarders tab, in the selected domain’s Forwarders list, verify that the IP addresses match those specified by your design.

    No existing DNS infrastructure

    No additional configuration is necessary.

    In this environment, if you want to configure internal DNS servers to resolve queries for external names, then configure this DNS server to forward unresolved queries to an external server, such as one in your perimeter network, or one hosted by an Internet service provider.