Check out http://YouTube.com/ITFreeTraining or http://itfreetraining.com for more of our always free training videos.
Globalnames allow a domain name as short as .apple, .xbox and .intranet to be used. This video looks at how to configure Windows DNS to use names like these on your internal network and also how global names will be used in the future on the internet.
Download the PDF handout http://ITFreeTraining.com/handouts/dns/dns-global-names.pdf
The first Microsoft networks used a peer to peer style system. Each computer had a computer name that was based on the NetBios standard and in the case of Microsoft networks this was limited to 15 characters. Networks had to be directly connected to each other as NetBios was not routable. However, later on, the ability to route network traffic was added to NetBios networks. This meant that on a NetBios network there could not be two computers with the same name. In order to achieve this, DNS had to be used rather than NetBios in which you could have two computers with the same name as long as the fully qualified domain name was different. For example, you could have fileserver.itfreetraining.com and fileserver.backup.itfreetraining.com on the same network as the full qualified domain names are different; however, notice that first part of the name is the same. This was not possible with NetBios.
From a user prospective, they want to be able to type in a short simple name to access a server. For example enter in NYDC1 rather than NYDC1.ITFreeTraining.local. To allow this to happen automatically Windows adds a DNS suffix to the name. This makes it simple for the user, however means that the DNS suffixes that Windows will used need to be configured on the computer. Global Name essentially allows a short simple name to be used without the need for a DNS suffix to be configured on the computer. This is the biggest noticeable missing feature from old NetBios system. In the old network NetBios system, all names were short names and thus were easy for the user to use. With DNS short names cannot be used like this and DNS requires the whole fully qualified domain name to be either entered in or Windows to automatically add a DNS suffix to the short name. So what is a global name? A global name is a short name that is compatible with DNS that allows the user to enter in a short name rather than a long name and does not require a DNS suffixes to be added by Windows to the name. This gives the user the most missed feature of NetBios networking while still being able to use DNS so, effectively, gives them the best of both worlds, that is being able to use a simple name referred to as a single label name in order to access resources on the network.
A DNS suffix is the last part of the domain, for example ITFreeTraining.com, HighCostTraining.com or example.com. If these 3 DNS suffixes were configure on a computer and you attempted to ping the address fs1 the following would occur. FS1.ITFreeTraining.com would be tried for a match. If no match was found, FS1.HighCostTraining.com would be tried, if there was no match here then FS1.example.com would be tried. If no match was found here the computer would report that the address was not resolvable. Notice that it means that 3 DNS addresses have to be checked with the DNS server to see if any of these are resolvable. If you have a large network with a lot of suffixes this means more addresses will need to be tried before the address is returned as not resolvable. If you want an address to be resolvable by all computers in the forest for a single label name, for example you want to create an address called intranet, this could be created and accessible to all computers in the forest without the need to configure a single DNS suffix on any computer in the forest.
Description to long for YouTube. Please see the following link for the rest of the description.
“Deploying a GlobalNames Zone” http://technet.microsoft.com/en-us/library/cc731744.aspx
“Add a GlobalNames Zone Service Location (SRV) Resource Record to a Forest” http://technet.microsoft.com/en-us/library/cc794952(v=WS.10).aspx
“Windows Internet Name Service” http://en.wikipedia.org/wiki/Windows_Internet_Name_Service
Great! thank you. you are awesome.
A few questions. In what order are these globalnames resolved in relation to the other zones. Let’s say intranet in itfreetraining.local points to svr2 and in globalnames to svr1. The client computer is a member of the itfreetraining.local domein. When it tries to ping ‘intranet’ which IP is returned? Can the order be changes (e.g. can globalnames override suffix search).
My last question is not about GlobalNames, but is about the remark that dynamic updates should be disabled. Does this implies that dynamic updates are by default enabled in Windows DNS?
On my DNS server I need to specify which server is allowed to make dynamic dns updates. On my network that is only one server, the DHCP server. I’ve also setup DNSSEC for authentication and verification. I once had a ‘guest’ on the wifi network that was trying to spoof the IP of the DHCP server in order to make changes to the DNS server. My firewall was able to stop the attack as the IP was coming from the wrong network interface (eth2 instead of eth0)..
I don’t ever comment but I wanted to thank you for these videos. I’m currently working on my MCSA for 2012 R2 and just passed the 410 test.
I’ve been watching your videos for a while and they always clears up whatever has me confused after reading material from a book.
Great excellent video tutorial thank you ITfreetraining.
Sir I Would like To Know Why We Need To Use GlobalNames While we Have In Hand CName Record ?
Thanks for the explanation.
Perfectly understood.BETTER THAN MU TEXTBOOK
Awesome video. Very easy to grasp.
in my test lab I created cname for my FQDN , inside the Forward lookup zone, which is working fine without creating GlobalName zone , I’m now confused I think I missed something to understand, why we need GlobalName if the cname do the job ?? .. could you please explain a bit morethanks a lot for your all great videos.regards
Great explanation way, first you explain then you perform the practical this is awesome. Thank you keep uploading such videos 🙂 thumbs up!!!!
IT Free Training is the best channel for IT professional
Thanks for the explanation it was great.
For those of you studying for the MCSA
Instead of using dnscmd.exe you can use powershell to enable the same thing.
Step1 – Enable the DNS Server for Single-label quires.
(Run on the DNS Server)
Set-DNSServerGlobalNameZone -Enable $True -Passthru
Step2 – Create a Primary DNS Zone AD Integrated with dynamic updates turned off. Replicate Forest Wide. Name "GlobalNames"
Add-DNsServerPrimaryZone -Name "GlobalNames" -ReplicationScope "Forest" -PassThru
Step3 – Add a CNAME record for each host you wish to provide a single-label name for.
Add-DNsServerResourceRecordCName -Name "TEST" -HostNameAlias "TestSRV01.Contoso.com" -ZoneName "GlobalNames"