none
GNZ

Answers

  • Hello,

    it can not replace WINS. 

    It is just providing NetBIOS name resolution support for applications that are using IPv6. 

    It can not replace it as it have not the same concept. As an example, records have to be added manually on your CNZ whild on WINS it is updated automatically.

    More about GNZ here: http://www.petri.co.il/windows-DNS-globalnames-zone.htm

     


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified IT Professional: Enterprise Administrator

    • Proposed as answer by MYousufAli Sunday, August 14, 2011 11:35 AM
    • Marked as answer by uzygr8 Wednesday, August 17, 2011 2:10 AM
    Sunday, August 14, 2011 9:04 AM
  • The purpose of the GNZ is to allow you to have a single zone of DNS records that is "pasted" on all of your authoritative zones. If you only have one zone, there is really no value to deploying GNZ in a single domain environment. It will only increase administrative burden.

    If you have only one domain then any time a user types in a short name (e.g. "accounting") the DNS client will append the domain name (or domain names) from the search suffix list and will resolve "accounting.corp.domain.com" on behalf of the client application. The client will never actually attempt to resolve the short name "accounting". If you have a small number of domains then you may wish to set the search suffix list on all of your clients to include all of your domains (via group policy). This will give you the illusion of a flat namespace without having to go to the trouble of deploying and maintaining a GNZ. However, if you have a large number of domains you will eventually reach a point where there are too many to deploy to all clients. In this case the GNZ can be used to give flat namespace functionality without client configuration.

    • Proposed as answer by Mr XMVP Sunday, August 14, 2011 12:02 PM
    • Marked as answer by uzygr8 Wednesday, August 17, 2011 2:11 AM
    Sunday, August 14, 2011 11:36 AM

All replies

  • Hello,

    it can not replace WINS. 

    It is just providing NetBIOS name resolution support for applications that are using IPv6. 

    It can not replace it as it have not the same concept. As an example, records have to be added manually on your CNZ whild on WINS it is updated automatically.

    More about GNZ here: http://www.petri.co.il/windows-DNS-globalnames-zone.htm

     


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified IT Professional: Enterprise Administrator

    • Proposed as answer by MYousufAli Sunday, August 14, 2011 11:35 AM
    • Marked as answer by uzygr8 Wednesday, August 17, 2011 2:10 AM
    Sunday, August 14, 2011 9:04 AM
  • The purpose of the GNZ is to allow you to have a single zone of DNS records that is "pasted" on all of your authoritative zones. If you only have one zone, there is really no value to deploying GNZ in a single domain environment. It will only increase administrative burden.

    If you have only one domain then any time a user types in a short name (e.g. "accounting") the DNS client will append the domain name (or domain names) from the search suffix list and will resolve "accounting.corp.domain.com" on behalf of the client application. The client will never actually attempt to resolve the short name "accounting". If you have a small number of domains then you may wish to set the search suffix list on all of your clients to include all of your domains (via group policy). This will give you the illusion of a flat namespace without having to go to the trouble of deploying and maintaining a GNZ. However, if you have a large number of domains you will eventually reach a point where there are too many to deploy to all clients. In this case the GNZ can be used to give flat namespace functionality without client configuration.

    • Proposed as answer by Mr XMVP Sunday, August 14, 2011 12:02 PM
    • Marked as answer by uzygr8 Wednesday, August 17, 2011 2:11 AM
    Sunday, August 14, 2011 11:36 AM
  • GNZ is not a replacement for WINS.  However, for a network without WINS that may require this single label support, GNZ may fill that need.  GNZ is not commonly deployed and should be used only for specific scenarios. 

    Here is a high level summary...

    Understanding GlobalNames Zone in Windows 2008
    http://www.anitkb.com/2010/03/understanding-globalnames-zone-in.html

     


    anITKB Visit anITKB.com, an IT Knowledge Base.
    facebook Follow me on Facebook.
    Sunday, August 14, 2011 8:51 PM