Single-label names (GlobalNames zone)

kamsz
Note by , created over 5 years ago

Microsoft 70-410 (Networking) Note on Single-label names (GlobalNames zone), created by kamsz on 08/13/2013.

Eye 134
Pin 0
Balloon left 0
Tags
kamsz
Created by kamsz over 5 years ago
Authenticated Firewall Bypass
kamsz
Security policies
kamsz
DHCP Relay agent
kamsz
A-level Sociology Quiz
Chuck Amobi
Plant Structure and Photosynthesis
Evangeline Taylor
Hardware, Software and Networking
dphillips211
2.1.6 Networks
Jake Youd
ISATAP
kamsz
Wireless Networking
Tunds
DHCP Failover
kamsz

Page 1

A common requirement in computer networks is the ability to resolve simple, single-label names. The use of single-label names makes it possible for a computer to access hosts such as file and Web servers by using short, easy-to-remember names instead of the fully qualified domain names (FQDNs) that form the default naming convention for Domain Name System (DNS). 

Deploying a GlobalNames zone The specific steps for deploying a GlobalNames zone can vary somewhat, depending on the AD DS topology of your network.Step 1: Create the GlobalNames zone The first step in deploying a GlobalNames zone is to create the zone on a DNS server that is a domain controller running Windows Server 2008. The GlobalNames zone is not a special zone type; rather, it is simply an AD DS-integrated forward lookup zone that is called GlobalNames. Step 2: Enable GlobalNames zone support The GlobalNames zone is not available to provide name resolution until GlobalNames zone support is explicitly enabled by using the following command on every authoritative DNS server in the forest: dnscmd <ServerName> /config /enableglobalnamessupport 1 where ServerName is the DNS name or IP address of the DNS server that hosts the GlobalNames zone. To specify the local computer, replace ServerName with a period (.), for example, dnscmd . /config /enableglobalnamessupport 1. Step 3: Replicate the GlobalNames zone To make the GlobalNames zone available to all DNS servers and clients in a forest, replicate the zone to all domain controllers in the forest, that is, add the GlobalNames zone to the forest-wide DNS application partition.If you want to limit the servers that will be authoritative for the GlobalNames zone, you can create a custom DNS application partition for replicating the GlobalNames zone. Step 4: Populate the GlobalNames zone For each server that you want to be able to provide single-label name resolution for, add an alias (CNAME) resource record to the GlobalNames zone. Step 5: Publish the location of the GlobalNames zone in other forests If you want DNS clients in other forests to use the GlobalNames zone for resolving names, add service location (SRV) resource records to the forest-wide DNS application partition, using the service name _globalnames._msdcs and specifying the FQDN of the DNS server that hosts the GlobalNames zone.In addition, you must run the dnscmdServerName/config /enableglobalnamessupport 1 command on every authoritative DNS server in the forests that do not host the GlobalNames zone.

Additional considerations By default, an authoritative DNS server uses local zone data first to respond to a query, before trying the GlobalNames zone to see if the name exists. If there is no relevant data in the GlobalNames zone and resolution using suffixes fails, resolution fails over to WINS. Querying local zone data first is a performance optimization.  Dynamic updates that are sent to an authoritative DNS server are checked against GlobalNames zone data first before being checked against local zone data. This ensures that GlobalNames zone names remain unique.  No software updates are required for clients to enable them to resolve the names that are configured in the GlobalNames zone. Primary DNS suffix, connection-specific suffixes, and the DNS suffix search list continue to work as usual. DNS client registration is not affected unless a computer tries to register a name that is already configured in the GlobalNames zone. 

New Page