DNS - GlobalNames zone

All Replies

• Thursday, May 10, 2007 5:13 AMDeji Akomolafe

   
  

  0

  Sign In to Vote
  Will someone from MS please chime in on this? There is nothing in the docs and nothing in the help files.
  • Reply
  • Quote

   
• Thursday, May 10, 2007 9:47 AMnExoRek

   
  

  0

  Sign In to Vote

  on the last chat there was an answer, that you need to simply manually create zone name 'GlobalNames'.

  but i've tried that and it seems to be not working...

   

  as i understood from the conversation - the mechanism is implemented and working but not yet exposed.. i am too still waiting for some answer ):

   

  • Reply
  • Quote

   
• Thursday, May 10, 2007 8:50 PMLibby Meren - MS

   
  

  0

  Sign In to Vote

  To create a global names zone, just create a zone with the name 'GlobalNames'.

   

  There will be a deployment guide detailing a GlobalNames zone creation posted shortly. I'll post an update in this thread with the location once it's available.

  • Reply
  • Quote

   
• Tuesday, May 15, 2007 6:16 PMLibby Meren - MS

   
  

  0

  Sign In to Vote
  A DNS GlobalNames Zone Deployment doc has just been published at:

  http://download.microsoft.com/download/a/5/7/a575d225-e82e-4361-a830-9fc94ab2d099/DNS-GlobalNames-Zone-Deployment.doc

   

   

  • Reply
  • Quote

   
• Saturday, May 19, 2007 5:39 AMDeji Akomolafe

   
  

  0

  Sign In to Vote

  Thank you, Libby. Unfortunately, GlobalNames still do not work. Still can't resolve single-label names even though the names are showing up in their respective zones, and the corresponding cname is showing up in the GlobalNames zone.

   

  It's probably me, but it'd be helpful if you (or someone else) could please confirm that the instructions in the doc are accurate and does get you a successful GlobalNames test in a multi-domain, single-forest configuration.

   

  Also, I am wondering what the following command is supposed to do, and how it's supposed to make the CNAME so created resolvable:

   

  dnscmd /RecordAdd itgroup.corp.contoso cweb CNAME cweb.itgroup.corp.contoso.com

   

  This command is repeated several times in the doc and this is leading me to believe that it could not have been a tyop and that my not understanding the logic is due to my unfamiliarity with this GlobalNames thingy. This would probably explain why my tests are failing.

   

  Thanks

  • Reply
  • Quote

   
• Sunday, May 20, 2007 9:59 AMnExoRek

   
  

  0

  Sign In to Vote
  you wrote 'the names are showing up in their respective zones, and the corresponding cname is showing up in the GlobalNames zone' - how did you mange that? i was trying to make it step-by-step with documentation and globalnames zone is empty. the command provided is creating simple cname in forward lookup zone.
  • Reply
  • Quote

   
• Monday, May 21, 2007 3:53 AMDeji Akomolafe

   
  

  0

  Sign In to Vote

  I manually created the CNAME records the GlobalNames zone for each corresponding static DNS A record.

   

  For example, for BigServer in my AD-intg mydomain.tld zone, I created a CNAME "BigServer" in the GlobalNames zones mapped to BigServer.mydomain.tld That is the way "Globalnames" zone concept was explained to me a long time ago when the idea was first brought up. Unfortunately, this is not how the dnscmd command that is included in this document is doing it, which leads me to one of 3 conclusion:

  1.  The document is wrong

  2.  They have changed how Globalnames concept is supposed to work

  3.  I am grossly misunderstanding the concept.

   

  In any case, I need help.

  • Reply
  • Quote

   
• Monday, May 21, 2007 2:30 PMnExoRek

   
  

  0

  Sign In to Vote

  ok. so i have done exactly the same.

  and with a very same effect - so i think the problem is not misunderstanding (;

  • Reply
  • Quote

   
• Monday, May 21, 2007 7:01 PMDeji Akomolafe

   
  

  0

  Sign In to Vote
  So now we just wait for the relevant MS resource to come in and help us out here
  • Reply
  • Quote

   
• Sunday, May 27, 2007 1:46 AMLibby Meren - MS

   
  

  0

  Sign In to Vote

  Hi All,

   

  It appears that there were some areas of the doc that need to be amended. While this is going through the publishing process, here are some corections:

  1. The command in the document:
     dnscmd /RecordAdd itgroup.corp.contoso cweb CNAME cweb.itgroup.corp.contoso.com
     Should be replaced with:
     dnscmd /RecordAdd  GlobalNames cweb CNAM cweb.itgroup.corp.contoso.com
  2. In order to turn on GNZ, you need to run the following dnscmd on each DNS server in the forest:
     dnscmd <server name> /EnableGlobalNamessupport 1
     Note: to turn off GNZ support, run the same command with "/Enableglobalnamessupport 0"

  Please accept my apologies for the confusion, and let me know if there are further problems.

   

  Thanks,

   

  Libby

   

  • Reply
  • Quote

   
• Sunday, May 27, 2007 3:18 PMnExoRek

   
  

  0

  Sign In to Vote

  i think you are using newer build if it works. i receive:

   

  Code Snippet

  Unknown Command "/EnableGlobalNamessupport" Specified -- type DnsCmd -?.

   

  using w2k8 b3
  • Reply
  • Quote

   
• Tuesday, May 29, 2007 5:27 AMDeji Akomolafe

   
  

  0

  Sign In to Vote

  The correct syntax is:

  
  

  Code Snippet

  dnscmd /config /EnableGlobalNamessupport 1

   

  Of course, it still doesn't appear to be working as advertized.

   

  However, I am now able to nslookup a single-labelled name of a server (ServerA) that resides in a.b.c, with a corresponding cname in the global zone, from a client  in b.c, and have it returned to me as ServerA.b.c
  

  This is progress. At least, I can see the concept working. We just need better documentation now - documentation from an ACTUAL implementation.

  • Reply
  • Quote

   
• Saturday, June 02, 2007 12:57 AMDeji Akomolafe

   
  

  0

  Sign In to Vote

  I can now confirm that this is working as described.

  The doc is incorrect in the syntax of dnscmd, and, as stated above, it ommits the critically important step of enabling support for global names resolution on DNS server.

   

  So, here are the things that you need to change in order to get GNZ resolution working:

  • create an AD-intg zones called globalnames
  • set the scope of replication for all DNS servers in the forest
  • No dynamic update
  • Enable GNZ support on each DNS server by doing the following:

  Code Snippet

  dnscmd /config /EnableGlobalNamessupport 1

   

  Restart DNS service on each DNS server

   

  Now you are ready to start creating records. For each record that you want to be able to resolve across the forest, you will create a corresponding CNAME in the globalnames zone.  Say you have 3 domains in your forest, and each contains the following important servers:

  • Domain1.loc has 2 servers Dom1Srv and BigApple
  • Domain2.loc has 2 servers tarpit and Armpit
  • domain3.loc has 2 servers slackjaw and Jawbone

   you want to be able to reach each of these servers from any of the domains using a single-labelled query, the following will be the records your create in the Globalnames zone:

  • Dom1srv CNAME Dom1srv.domain1.loc
  • bigapple CNAME bigapple.domain1.loc
  • tarpit CNAME tarpit.domain2.loc
  • armpit CNAME Dom1srv.domain2.loc
  • slackjaw CNAME slackjaw.domain3.loc
  • jawbone CNAME jawbone.domain3.loc

  You should note that, as in normal CNAME creation, there is no requirement that the label of the CNAME should match the label of A record. In my example above, the following would have worked as well:

  • slickwilly CNAME slackjaw.domain3.loc

  If you are not the goooey type, then the following is the correct dnscmd syntax:

  Code Snippet

  dnscmd mydnsservername /recordadd GlobalNames slickwilly CNAME slackjaw.domain3.loc

  • Reply
  • Quote

   
• Monday, June 11, 2007 4:39 PMDNRvNext

   
  

  0

  Sign In to Vote

  Thanks Deji, this is really helpful. Does anyone have any idea when Microsoft will be updating and releasing a new version of the document?

  Nelson Ruest, Windows Server MVP

  • Reply
  • Quote