Understand more on Microsoft DNS Server (Part V)

Global Name Zone (GNZ)

In Windows Server 2008 supports a special GlobalNames Zone (GNZ) feature use to help customers migrate to DNS for all name resolution the DNS Server role. Some customers in particular require the ability to have the static, global records with single-label names (such as “Mail” instead of “mail.testlab.com”) that WINS currently provides.

• GNZ is not intended to support the single-label name resolution of records that are dynamically registered in WINS, records which typically are not managed by IT administrators.

• GNZ zone by default does not exist.

• Only compatible with DNS servers running Windows 2008 Server and cannot replicate to servers running earlier version of Windows Server

How it GNZ works

  • The company Contoso has an internal Web site which users typically access by typing http://mail in the browser address bar.
  • The fully qualified domain name (FQDN) of the Web server is mail.mis.corp.testlab.com.
  • Group Policy for all the clients is configured with a DNS suffix search list consisting of the following:
    • engineering.corp.contoso.com
    • accounting.corp.contoso.com
    • mis.corp.contoso.com
    • corp.contoso.com

How the name is resolved:

  1. A user types in http://mail into the browser address bar on a computer that is joined to the engineering.corp.contoso.com domain.
  2. The browser calls the GetAddrInfo() function to resolve the name mail.
  3. GetAddrInfo() invokes DNS Client to resolve the name.
  4. DNS Client sends out the following qualified queries (based on the suffix search list):
    1. mycontoso.engineering.corp.contoso.com -> Name Error
    2. mycontoso.accounting.corp.contoso.com -> Name Error
    3. mail.mis.corp.contoso.com -> Success

Step by Step Setup GNZ

This must be performed by either manually changing the server’s registry, or by using the command line:

  1. Click Start, right-click Command Prompt, and then click Run as Administrator.
  2. Type the following command, then press Enter:

Dnscmd servername /config /enableglobalnamessupport 1

Ensure GlobalNames Zone Functionality has been enabled on each DNS server in the forest

  1. Open the DNS console from the Administrative Tools folder.
  2. In the console tree, right-click a DNS server, and then click New Zone to open the New Zone Wizard. You can also do this by right-clicking the Forward Lookup Zones and selecting Create a New Zone.

5. Choose an appropriate storage method and replication scope for the zone. Microsoft’s recommendations are that you store the zone in AD DS and replicate it to all domain controllers that are DNS servers in the Forest. This will create a new AD DS integrated zone called GlobalNames which is stored in the forest-wide DNS application partition.

6. Give the new zone the name of GlobalNames. Click Next.

Note: This is not case sensitive: globalnames is supported but make sure no other zone name GlobalNames exist

7. In the Dynamic Updates page click Next then Finish

Note: Do NOT allow for dynamic updates as all the records inside will be manually created.

8. Click Finish to finish the zone creation wizard.

Advertisements
This entry was posted in Windows Server. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s