Your network contains an Active Directory forest named fabrikam.com. The forest contains a DNS server named Server1. You need to configure Server1 to resolve single-label names. What should you do?

Question

Options

• ACreate a DNS zone named GlobalNames.
• BCreate a DNS zone named GlobalNames.
• CCreate a DNS zone named RootNames.
• DCreate a DNS zone named RootNames.

• A
  74% (43)
• B
  7% (4)
• C
  3% (2)
• D
  16% (9)

Explanation

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. For information about creating a primary forward lookup zone, see Add a Forward Lookup Zone. 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 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 /enableglobalnamessupport1. 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. For more information, see Change the Zone Replication Scope. 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. For more information, see Understanding DNS Zone Replication in Active Directory Domain Services. 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. For more information, see Add an Alias (CNAME) Resource Record to a 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. For more information, see Add a Resource Record to a Zone and Service Location (SRV) Resource Record Dialog Box. 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.

No community discussion yet for this question.