【正文】 domain names. Organizations that have works with their own DNS servers can create domains for their internal use. As the next section explains, these internal DNS namespaces can be—but are not required to be—subdomains of a public Inter domain name. Designing a DNS namespace You can design an external namespace that is visible to Inter users and puters. You can also design an internal namespace that is visible only to users and puters that are in your internal work. Organizations that require an Inter presence and an internal namespace must deploy both an internal and an external DNS namespace and manage each namespace separately. In this case, we remend that you make your internal domain a subdomain of your external domain. For example, an anization that has an external domain name of might use the internal domain name . Using an internal domain that is a subdomain of an external domain has the following advantages: ?? Requires you to register only one name with an Inter name authority even if you later decide to make part of your internal namespace publicly accessible. ?? Ensures that all of your internal domain names are globally unique. ?? Simplifies administration by enabling you to administer internal and external domains separately. 9 ?? Allows you to use a firewall between the internal and external domains to secure your DNS deployment. If you want to deploy an AD DS domain for each division in your anization, you can use your internal domain as a parent for additional child domains that you create to manage those divisions. Child domain names are immediately subordinate to the domain name of the parent. For example, a child domain for a manufacturing division that you add to the namespace might have the domain name . Creating an Inter DNS domain name An Inter DNS domain name has a TLD name, such as ., ., or .edu, and a unique subdomain name that the domain owner chooses. For example, a pany named Contoso Corporation would probably choose as its Inter domain name. Before you register an Inter DNS domain, conduct a preliminary search of the Inter to confirm that the DNS domain name that you want to use is not already registered to another anization. If the domain name that you want to use is available, contact your Inter service provider (ISP) to confirm that the domain name is available and to help you register your domain name. Your ISP might set up a DNS server on its own work to host the DNS zone for your domain name or it might help you set up a DNS server on your work for this purpose. Creating internal DNS domain names For your internal domains, create names that are related to your registered Inter DNS domain name. For example, if you register the Inter DNS domain name for your anization, use a DNS domain name such as for the internal, fully qualified DNS domain name and use CORP as the NetBIOS name. If you want to deploy DNS in a private work, but you do not plan to create an external namespace, you should still register the DNS domain name that you create for your internal domain. If you do not register the name, and you later attempt to use it on the Inter or you use it to connect to a work that is connected to the Inter, the name might be unavailable. Creating DNS puter names When you create DNS names for the puters on your work, develop and follow a logical DNS puternaming convention. This makes it possible for users to remember easily the names of puters on public and private works, which facilitates access to work resources. Use the following guidelines when you create DNS names: ?? Select puter names that are easy for users to remember. ?? Identify the owner of a puter in the puter name. For example, andrewdixon indicates that Andrew Dixon uses the puter, and pubsserver indicates that the puter is a server that belongs to the Publications department. ?? As an alternative, select names that describe the purpose of the puter. 10 For example, a file server named pastaccounts1 indicates that the file server stores information related to past accounts. ?? Do not use capitalization to convey the owner or purpose of a puter. DNS is not case sensitive. ?? Match the AD DS domain name to the primary DNS suffix of the puter name. The primary DNS suffix is the part of the DNS name that appears after the host name. ?? Use unique names for all puters in your anization. Do not assign the same puter name to different puters in different DNS domains. For example, do not use such names as and . Also, do not use the same puter name when a puter is configured to run different operating systems. For example, if a puter can run Windows Server 2020 or Windows Vista, do not use the same puter name for both operating systems. ?? Use ASCII characters to ensure interoperability with puters running versions of Windows earlier than Windows 2020. For puter and domain names, use only the characters A through Z, 0 through 9, and the hyphen (). Do not use the hyphen as the first character in a name. In particular, the following characters are not allowed in DNS names: ?? ma (,) ?? tilde (~) ?? colon (:) ?? exclamation point (!) ?? at sign () ?? number sign () ?? dollar sign ($) ?? percent sign (%) ?? caret (^) ?? ampersand (amp。 2020 Microsoft Corporation. All rights reserved. Active Directory, SharePoint, Windows, Windows Server, Windows Vista, the Windows logo, and the Microsoft logo are trademarks of the Microsoft group of panies. All other trademarks are property of their respective owners. Contents StepbyStep Guide for DNS in Small Networks ........................................................................5 Planning DNS.........................................................................................................................6 Understanding t