The GlobalNames zone is compatible only with DNS servers running Windows Server 2008 and Windows Server 2008 R2. Therefore, it cannot replicate to servers running earlier versions of Windows Server.
There are three basic steps in deploying a GlobalNames zone.
1. Enable GlobalNames zone support. You can perform this step before or after you create the zone, but you must perform it on every DNS server to which the GlobalNames zone will be replicated.
At an elevated command prompt, type the following: dnscmd . /config /enableglobalnamessupport 1
In this case the “.” is used to represent the local server. If you want to enable GlobalNames zone support on a remote server, substitute the “.” for the DNS server name.
2. Create the GlobalNames zone. The next step in deploying a GlobalNames zone is to create the zone on a DNS server that is a domain controller running Windows Server 2008 or Windows Server 2008 R2. The GlobalNames zone is not a special zone type; rather, it is simply an Active Directory–integrated forward lookup zone that is called GlobalNames. When you create the zone, make sure to select the option to replicate zone data to all DNS servers in the forest. (This option appears on the Active Directory Zone Replication Scope page of the New Zone Wizard.)
3. Populate the GlobalNames zone. For each server for which you want to be able to provide single-label name resolution, create an alias (CNAME) resource record in the GlobalNames zone. The name you give each CNAME record represents the single-label name that users will use to connect to the resource. Note that each CNAME record points to a host record in another zone.
exam tip
Quick check
■ Why would you use a GlobalNames zone?
Quick check answer
■ To facilitate the resolution of single-label computer names in a large network.
PRACTICE
deploying a globalnames Zone
In this practice, you will create the GlobalNames Zone to enable connectivity to a specific single-label name throughout an Active Directory forest.
ExERCIsE 1 Enabling the GlobalNames Zone
In this exercise, you will enable the GlobalNames zone on Dcsrv1. In a production environment, you would need to perform this step on every DNS server in the forest.
1. Log on to Nwtraders from Dcsrv1 as a domain administrator. 2. Open an elevated command prompt.
3. At the command prompt, type dnscmd . /config /enableglobalnamessupport 1. Note the space in this command after the “.” You receive an output message indicating that the Registry property was successfully reset.
ExERCIsE 2 Creating the GlobalNames Zone
In this exercise, you will create a new DNS forward lookup zone named GlobalNames on Dcsrv1. 1. While you are logged on to Nwtraders from Dcsrv1 as a domain administrator, open
DNS Manager.
2. In the DNS Manager console tree, right-click the Forward Lookup Zones container, and then choose New Zone.
3. On the Welcome page of the New Zone Wizard, read the text, and then click Next. 4. On the Zone Type page, read all the text on the page. Leave the default selections of
Primary and Store The Zone In Active Directory, and then click Next.
5. On the Active Directory Zone Replication Scope page, select To All DNS Servers In This Forest, and then click Next.
6. On the Zone Name page, type globalnames, and then click Next.
7. On the Dynamic Update page, select the Do Not Allow Dynamic Updates option, and then click Next. You should choose the option because dynamic updates are not supported with the GlobalNames zone.
8. After the Completing The New Zone Wizard page, read the text, and then click Finish. In the DNS Manager console tree, the new GlobalNames zone appears.
ExERCIsE 3 Adding Records to the GlobalNames Zone
In this exercise, you will add records to the GlobalNames zone so that you can later test its functionality.
1. While you are still logged on to Nwtraders from Dcsrv1 as a domain administrator, in the DNS Manager console tree, select and then right-click the GlobalNames zone, and then choose New Alias (CNAME).
2. In the New Resource Record dialog box, in the Alias Name text box, type mail. 3. In the Fully Qualified Domain Name (FQDN) For Target Host text box, type
dcsrv1.nwtraders.msft, and then click OK. A new alias (CNAME) record with the name “mail” now appears in the GlobalNames zone.
ExERCIsE 4 Testing the GlobalNames Zone
In this exercise, you will attempt to resolve the name of the new record you have created. The GlobalNames zone is used to resolve single-name tags anywhere in an Active Directory forest. 1. Log on to Nwtraders from Boston as a domain administrator.
2. Open an elevated command prompt.
3. At the command prompt, type ping mail. Boston translates the name “mail” to dcsrv1.nwtraders.msft and then pings the address of that server. You know that this name has been resolved from the GlobalNames zone because there is no record in the Nwtraders.msft zone for a host or an alias named “mail.”
4. Log off both Dcsrv1 and Boston.
Lesson Summary
■ A DNS zone is a database containing records that associate names with addresses for a defined portion of a DNS namespace. To create a new zone on a DNS server, you can use the New Zone Wizard in DNS Manager. The New Zone Wizard enables you to choose a zone type, specify a forward or reverse lookup zone, set the zone replication scope, name the zone, and configure options for dynamic updates.
■ A primary zone provides original read-write source data that allows the local DNS server to answer DNS queries authoritatively about a portion of a DNS namespace. A secondary zone provides an authoritative, read-only copy of a primary zone or another secondary zone. A stub zone is similar to a secondary zone, but it contains only those resource records necessary to identify the authoritative DNS servers for the master zone.
■ When you create a new primary or stub zone on a domain controller, the Zone Type page gives you the option to store the zone in Active Directory. There are several advantages to integrating your DNS zone with Active Directory, including ease of management, the availability of multiple primary zones, and improved security.
■ When you do not store a zone in Active Directory, the zone is called a standard zone, and zone data is stored in text files on the DNS server.
■ When you create a new zone, two types of records required for the zone are auto- matically created: an SOA record and at least one NS record. The SOA record defines basic properties for the zone. NS records determine which servers hold authoritative information for the zone.
■ Aging in DNS refers to the process of using time stamps to track the age of dynami- cally registered resource records. Scavenging refers to the process of deleting outdated resource records on which time stamps have been placed.