windowsserver20xxdns服务在小网络中的部署

windowsserver20xxdns服务在小网络中的部署内容摘要：

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。 )  apostrophe (39。 )  period (.), except as a separator between names  parentheses (())  braces ({})  underscore (_)  The number of characters in a name must be between 2 and 24.  Avoid nonstandard TLDs such as .local. Using a nonstandard TLD will prevent you from being able to register your domain name on the Inter. 11 Installing and Configuring AD DS and DNS When you create a new Active Directory Domain Services (AD DS) domain, the Active Directory Domain Services Installation Wizard installs the Domain Name System (DNS) server role by default. This ensures that DNS and AD DS are configured properly for integration with each other. Important Before you install AD DS and DNS on the first domain controller server in a new domain, ensure that the IP address of the server is static。 that is, that it is not assigned by Dynamic Host Configuration Protocol (DHCP). DNS servers and Active Directory domain controllers must have static addresses to ensure that clients can locate the servers reliably. To install DNS with AD DS in a new domain 1. Click Start, point to Administrative tools, and then click Server Manager. 2. In the tree pane, click Roles. 3. In the results pane, click Add Roles. 4. On the Before You Begin page, click Next. 12 5. On the Select Server Roles page, click Active Directory Domain Services, and then click Next. 13 6. On the Active Directory Domain Services page, read the information and then click Next. 7. On the Confirm Installation Selections page,。