Windows Server 2008 R2/windows 7 management Eight DNS new features and general management

The most notable improvements to DNS in 2008R2 are globalnames to replace wins

This article sets the IP of the domain controller for the preferred DNS of the network domain clients that often have friends. However, secondary DNS sets the IP for external DNS, and even the domain-controlled DNS option also sets the secondary DNS to external DNS servers. This is unscientific, and domain control is best not to use external DNS.

What's the solution? This article will introduce you to DNS forwarders, as well as globalnames zones and some common DNS records

This article is divided into 1.dns common records of the creation of 2.dns transponder settings 3. GlobalNames area creation and management

About GlobalNames excerpt from Microsoft explained as follows:

A common requirement in computer networks is the ability to parse simple single label names. With a single label name, you can have your computer access a host such as a file server and a WEB server by using a short, accessible name, rather than using the fully qualified domain name (FQDN) of the default naming convention that makes up the domain Name System (DNS). To be able to use single label names, many networks have deployed Windows Internet Name Service (WINS) technology and WINS servers in their environments. As a name Resolution Protocol, WINS is an alternate option for DNS. It is an old service that uses NetBIOS (NetBT) on TCP/IP. WINS and NetBT do not support the Internet Protocol version 6 (IPV6) protocol, so they will be phased out in many networks. To help network administrators switch to DNS to resolve all names, the DNS server role in Windows Server 2008 supports a special named zone called GlobalNames. By deploying a zone with this name, you can use static global records with a single label name, rather than relying on WINS. These single label names typically refer to records of important, known, and widely used servers that have been assigned static IP addresses and that are currently managed by the IT administrator using WINS. The GlobalNames area is not designed to completely replace WINS. You should not use the GlobalNames zone to support name resolution of dynamically registered records in WINS, which are typically not managed by IT administrators. You cannot arbitrarily adjust the support for these dynamically registered records, especially for large customers with multiple domains or multiple forests.

1. Creation and management of DNS common records

After the default installation completes the domain controller, already has the DNS server as shown, the positive and negative areas have