Atps paulo

Planning DNS
DNS is the primary method for name resolution in the Microsoft® Windows Server™ 2003, Standard Edition; Windows Server 2003, Enterprise Edition; and Windows Server 2003, Datacenter Edition operating systems (collectively referred to as "Windows Server 2003" in this guide). DNS is a requirement for deploying the Active Directory® directory service. Integrating DNS with Active Directory enables DNS servers to take advantage of the security, performance, and fault tolerance capabilities of Active Directory.
Typically, you organize your DNS namespace (the association of domains, subdomains, and hosts) in a way that supports how you plan to use Active Directory to organize the computers on your network. For more information about using Active Directory to organize your network, see "Designing the Active Directory Logical Structure" in Designing and Deploying Directory and Security Services on Microsoft Windows Server 2003 TechCenter (http://go.microsoft.com/fwlink/?LinkId=50361) or on Microsoft Download Center (http://go.microsoft.com/fwlink/?LinkId=50360).
Understanding the DNS Namespace
DNS is a hierarchical naming system. A DNS name includes the names of all of the DNS namespaces that it belongs to. The following illustration shows how the DNS namespace is organized.

The DNS namespace begins with a logical root domain that is not named, partly because it is implicit in all DNS names. The root domain in turn contains a limited number of subdomains that help organize the DNS namespace. These subdomains are called top-level domains (TLDs) because they are the highest-level or most inclusive part of the DNS namespace that people use. The names of these top-level domains are either functional or geographical.
Functional top-level domains suggest the purpose of the organization that has registered a subdomain in the top-level domain. Some of the most common functional top-level domain names are:
• The .com top-level domain, which is