For organizations with an Active Directory-Integrated DNS configuration, one of the challenges over the years has been the removal of Windows Internet Name Service, or WINS. Windows Server 2008 (WS2K8) introduces the GlobalNames zone (GNZ) where larger environments with multiple DNS suffixes can use a single name host across all domains.
How the GNZ works is by creating a zone that is resolvable without regard to the suffix order. The ideal scenario is for a host that may be called “intranet.corporate.company.net” and all clients across different domains, with their respective suffix configurations, can access the Intranet simply by putting “Intranet” in their Web browser. The other domains may have DNS suffixes such as: boston.company.net or engineering.boston.company.net. The Intranet server with the corporate.company.net DNS suffix can be accessed across all zones with the short name regardless of suffix.
To use the GNZ, there are a few planning points. First of all, you should not have a forward zone that you are already using called “GlobalNames,” that is going to be a problem! The DNS server needs to be WSK8, but domain controllers can be 2003. As a note for planning, the GNZ is currently not permitted to support dynamic updates, which is a reflection of the static nature of the zone. Lastly, the GlobalNames support needs to be enabled. This is done with the following command:
dnscmd DNSServerName /config /enableglobalnamessupport 1
Once you have the feature enabled, make a primary forward zone with the name “GlobalNames” within the DNS console. Once the zone is ready, you can make entries to the GNZ. When a request is made to the GNZ, the FQDN of the host is returned to the requesting client. So, in the example above, if a client from any subdomain of company.net tries to access “intranet,” it will resolve to the FQDN of intranet.corporate.company.net.
More information on GNZ can be found in the Microsoft DNS Server GlobalNames Zone Deployment guide.