Enter the correct email address of the person in charge to add to the DNS server or in each area managed on the DNS server.
For various reasons, the application uses this field to notify the DNS administrator. For example, query errors, error data returned in the query, and security issues are several ways available in this field. Since most Internet email addresses used in the email application contain AT symbols (@), these symbols must be replaced with a period (.) When entering an email address for this field. For example, "example.microsoft.com" should be used instead of "eXample@microsoft.com".
If you want to use Active Directory, use the directory integration store in order to make the area get the best effect and simplify configuration and troubleshooting.
With the integration with the area, you can simplify the network planning. For example, the domain controller of each Active Directory domain corresponds to the DNS server in direct one-to-one map. Because the same server computers are used in both topology, this can simplify the planning and troubleshooting of DNS and Active Directory replication issues.
If the DNS client is running Windows 2000, you can simplify the client in DNS to perform DNS dynamic updates. For example, you only need to use the server IP address of the corresponding domain controller close to each client for each client configuration for each client to use. If the client cannot update with its preferred server (because the server cannot be used), you can try the standby server. It allows clients to successfully update their records on another server on which the directory integration DNS area is loaded.
If you don't use Active Directory, pay attention to the failure point and configuration problem when dynamically updating with the standard primary type area.
If you do not use Active Directory, you need a standard primary type area to create and manage the area in the DNS namespace. In this case, a single-master update model will be used, and a DNS server is assigned a primary server of the area. As determined in the regional SOA record attribute, only the primary server can process the area update.
Therefore, be sure to configure the client to use the preferred DNS server using reliable and handleable and interpreted updates. Otherwise, the client cannot successfully update its host (a) or pointer (PTR) resource record (RR).
To configure DNS for clients with static configuration IP addresses, you may need to configure the following options:
The client's DNS host name (or name).
The client is used to help parse the main and alternate DNS servers of the DNS domain name.
Additional suffix lists for improving unqualified DNS names for searching and submitting DNS queries to resolve on the client.
Connect a unique dynamic update and registration behavior, such as whether the specific network card installed on the client is dynamically registered to the DNS server to configure the IP address it configures.
DNS definition
DNS is an abbreviation of domain name systems, a computer and network service naming system for organizing an domain hierarchy. DNS is named for TCP / IP networks, such as Internet, to locate computers and services through user-friendly names. When the user enters the DNS name in the application, the DNS service can resolve this name to additional information related to this name, such as an IP address.
For example, most users like to use a friendly name (for example, Example.Microsoft.com) to locate a computer such as a mail server or a web server on the web. The friendly name is easier to remember. However, the computer uses the digital address to communicate online. In order to easily use network resources, a name service such as DNS provides a method to map user-friendly computers or service names to digital addresses. If you use a web browser, you should also use DNS. DNS tool
Windows 2000 provides some utilities for managing and monitoring DNS servers and clients and resolving their system issues. include:
The DNS console is part of the management tool.
Command line utility, such as NSlookup, can be used to discover and solve DNS issues.
Log features, such as DNS Server Logs, you can use the Event Viewer to view the log. File-based logs can also be temporarily used as a high-level debug option to record and track the selected service event.
Performance monitoring utilities, such as statistics, you can use system monitor to measure and monitor activities of DNS servers.
DNS console
The main tools for managing the Windows 2000 DNS server are DNS console, which is provided in the Administrative Tools folder in the control panel. The DNS console is displayed as a Microsoft Management Console (MMC) snap-in to further integrate DNS management into all of your network management.
After installing the DNS server, you can use the DNS console to perform these basic management server tasks:
The new DNS server is initially configured.
Connect and manage local DNS servers on the same computer, or remote DNS servers on other computers.
Add and delete the forward and reverse search area as needed.
Add, delete and update resources in the area.
Modify the way the area storage and replication between the server.
Modify the server to process the query and dynamic update.
Modify the security of specific areas or resource records.
In addition, you can also perform the following tasks using the DNS console:
Execute the task of the maintenance server. You can start, stop, pause, or restore running servers, or manually update server data files.
Monitor the contents of the server cache, if needed, you can clear it.
Debug Advanced Server Options.
Configure and execute the aging and cleanup work of the old resource records stored in the server.
DNS domain name
The Domain Name System (DNS) was originally defined in RFCs 1034 and 1035. These RFC documents specify all elements of all implementations of the DNS-related software, including:
DNS Domain Namespace, which specifies hierarchies of the domain used to organize names.
Resource Record, which maps the DNS domain name to a specific type of resource information for use in a namespace or parsing names.
DNS server, it stores and responds to the name query for resource records.
DNS client, also known as parsing programs, it queries the server to search and resolve the name to the type of resource record specified in the query.
Cache work principle
DNS servers use recursive or iteration to handle client queries, they will find and obtain important information about DNS namespaces. This information is then cached by the server.
The buffer provides a subsequent query that accelerates the DNS parsing performance, while sufficiently reduces the query traffic associated with DNS on the network.
The resource record (RR) is temporarily caught when the DNS server recursively queries the client. The cached RR contains information obtained from the DNS server, and this information has absolute authority for the DNS domain name known in the recursive query executing the iterative query to the recursive query executing the client executing the client. Later, when other clients send new queries, the DNS server can use the cached RR information to respond to them when they issue a new query.
When the information cache, the living time (TTL) value is suitable for all cached RRs. As long as the TTL of the cache RR does not expire, the DNS server can continue to cache and use RR again when the query matches the client with these RRs. The cache TTL value used by RR in most regional configuration is assigned a "minimum (default) TTL", which is set for the launch authorization authority (SOA) resource record for the area. By default, the smallest TTL is 3600 seconds (1 hour), but can be adjusted, or the cache TTL is set separately on each RR. Reverse search
In most DNS searches, the client generally performs a forward search, and the forward search is a search for DNS names stored in another computer stored in the address (a) resource record. Such queries wish to use the IP address as the resource data of the response.
DNS also provides a reverse search process, allowing clients to use known IP addresses during the name query and search computer names based on its address. Reverse search takes a question and answer form, such as "Can you tell me the DNS name of the computer that uses IP address 192.168.1.20?"
This type of query is not supported in the design of DNS. Supporting the reverse query process may have a problem, namely the way DNS namespace organization and index names and IP address assignments are different. If the only way to answer the previous problem is to search in all domains in the DNS namespace, the reverse query will take a long time and require a lot of useful processing.
In order to solve this problem, special domain IN -ADDR.ARPA domains are defined in the DNS standard, and retain in the Internet DNS namespace to provide a reverse query in a practical way. In order to create a reverse namespace, the subdomain in the in -addr.arpa domain is the opposite order of the decimal number with the IP address.
Because the DNS name is different, when the IP address is read from left to right, they are interpreted in the opposite manner, so the domain is designed for each eight-bit byte value. When the IP address is read from left to right, it is the most specific information (IP network address) contained in the first part to the last eight byte (IP host address).
Therefore, when establishing in -addr.arpa domain tree, the order of the eight-bit byte of the IP address must be inverted. After this arrangement, when the IP address is assigned to the company, the IP address within the range of the IP-defined address category is located, can provide the company's management of the lower layer branches in the DNS IN-ADDR.ARPA tree.
Finally, in the IN-ADDR.ARPA domain tree required in DNS requires other resource record (RR) types, such as pointer (PTR) RR. This RR is configured to create a mapping in the reverse search area, which typically names RR corresponding to the host (a) of the DNS computer name in which the host is in the search area.
Change the server's primary DNS domain name
When you change your computer's DNS domain name, the ability to change the server main DNS domain name can depend on whether the computer is used as a domain controller.
If you run the server computer as a domain controller, the primary DNS domain name of the server computer is set to be the same as the name of the Active Directory domain that upgrades the server to the domain controller. To change this name, you must downgrade the server first so that it is no longer a domain controller. For the server that changes the parent DNS domain name in this case, the process of adding and deleting A and PTR RR when it is joined and leaving the Active Directory domain. In this case, you may only need to manually update the name server (NS) RR of the old DNS parent domain and the new DNS parent domain.
To change the DNS domain name without using the DNS server computer using Active Directory, such as domain member servers or standalone servers, some other changes and manual management may be required. For example, if the old DNS domain name and the new DNS domain name are in two different regions, such as region A (old areas) and zone B (new areas), you may need to change as follows: Changed in System Attributes " The main DNS suffix of this computer is restarted.
In area A, the host (a) RR of the server is deleted.
In the area B, the A RR of the server is added.
Update all starting authority (SOA) and Name Server (NS) RR in the area containing renamed DNS server names.
