Determining The Dns Configuration Method

By Author: Jasmine
Total Articles: 286
Comment this article

You can configure your Windows Server 2003 70-291 Exam server manually or you can allow it to be configured automatically during Active Directory installation. Manual configuration of DNS to support Active Directory is required if you are using a non-Windows Server 2003 DNS server or if you want to set up a configuration other than the default configuration set up during Active Directory installation. You can configure DNS manually using the DNS console. For details about manually configuring DNS for Active Directory, refer to the MCSA/MCSE Self-Paced Training Kit (Exam 70-291): Implementing, Managing, and Maintaining a Microsoft Windows Server 2003 Network Infrastructure (Microsoft, Press, 2003).
Although Active Directory requires that the DNS service he installed on your network, you can install DNS implementations other than Microsoft Windows Server 2003 DNS service. However, these other implementations might not have all of the features of Windows Server 2003 DNS. Therefore, you might not be able to take advantage of full DNS integration with Active Directory. For details about ...
... Active Directory interoperability with other DNS services, refer to the MCSA/MCSE Self-Paced Training Kit (Exam 70-291): Implementing, Managing, and Maintaining a Microsoft Windows Server 2003 Network Infrastructure.

Never use the same domain name twice. For example, Microsoft should not use the name microsoft.com for both its Internet and intranet root domains. If a
microsoft.com client attempts to connect to either the Internet or the intranet microsoft.com site, the domain that answers first is the one to which the client is connected.
Use only registered 70-291 practice test domain names. Register all second-level domain names,whether they are internal or external namespaces, with the InterNIC or other
authorized naming authority. For example, Microsoft should register its second-level domain name as microsoft.com. The company does not need to register
corp.microsoft.com because it is not a second-level domain name. Internal names that are second-level domain names should be registered to ensure access from
outside the corporate firewall.
You should always configure a Preferred and Alternate DNS server for all client computers, member servers, and domain controllers whenever possible. Without DNS, domain member computers are unable to find domain controllers. If you only configure a Preferred DNS server on (a) domain member computer(s) and that DNS server is unavailable for any reason, those domain member computers will be unable to locate a domain controller. If a client computer is unable to locate a domain controller, a large variety of connectivity and logon free Microsoft practice exam questions issues can occur.