Frizbits’ Bits

June 26, 2008

ICANN approves new top level domains.

Filed under: Uncategorized — Tags: , — frizbit @ 2:20 pm

Another breaking item in the news recently.  ICANN has approved custom top level domains.  In the past these top level domains (TLDs) were limited to .com, .net, .org (among others) and country codes like .us, .uk, etc.  Over the last few years others have been approved like .info, .travel, and .pro.  When these new rules go into effect an organization can decide on their own TLD.  Imagine a world with not just but,, burger.king, among millions of others.  How will we ever find anything anymore?  I imagine in the short term commercial organizations will keep at least their root presence in the traditional .com/.net/.org space.  Long term only time will tell but search engines certainly aren’t going away anytime soon.  Starting a new TLD will consist of jumping through numerous hoops as well as a significant investment in money.  Large registrars like Verisign will probably snap up a few new trendy TLDs to sell… .corp, .law, .whereeverthemoneyis.

One thing everyone seems to wonder is what will happen to .xxx.  This TLD has been repeatedly rejected by ICANN.  Do these rules open it up?  And who will have the corporate might to fight for the money available here?


Read more about it here.

December 3, 2007

New DNS zone fun

Filed under: Windows Server 2008 — Tags: , , — frizbit @ 11:22 am

Continuing on with my Windows Server 2008 studies I came across something new in DNS.  Since pretty much everyone would like WINS to go away we now have a replacement (sort of).  The GlobalNames zone in DNS.  This new zone will hold single label names similar to WINS.  For example if I have the FQDN in DNS, I can now create a CNAME record in the GlobalNames zone named simply server1.  But how do we resolve these names now?  Well, the order of operations is below….

1. Append the clients primary DNS suffix and try to resolve the name.
2. If that fails, try the other DNS suffixes in the configured search lists.
3. If that still fails, attempt to find name in the Global names zone.
4. Beyond that we can still fail over to WINS if it is still available.

So from this list GlobalNames appears to be the most useful in a multidomain environment.  We will still try all configured DNS suffixes first though, so keep that in mind.  A few other caveats exist for this new zone also.  First of all GlobalNames is forest wide and should be created as an AD integrated zone.  All DNS servers in the forest must be running Server 2008 to get this functionality.  It also doesn’t support dynamic registration of records (although a CNAME can point to a FQDN that is dynamically registered in another zone).  This means its not a total replacement for WINS.  It’s intended for managed records of important resources.

The search order above is very important. If in the example above I had multiple domains, all it would take is for someone to create a server named server1 in a domain in the DNS search order list and their server would resolve instead of my intended global name.

The Deployment guide whitepaper is available here.
I also found this extremely helpful in setting it up on a test server.

Create a free website or blog at