Almost every registrar has a feature that that allow you to “Register Nameserver”, they will tell you if you don’t do that, the nameserver may not able use on other domain, but have you wonder why?
“Error: Nameserver is not registered” – Almost every nightmare when register domain or modify domain nameserver.
First, we need to understand how the a domain name working in the internet. Says, you have a domain example.com and hosted somewhere in the world, and now you are visiting the website, this is what will happen in high level:
- You will first need to check who is the registry of the domain extension “.com” by checking from root server.
- Root server: “hey, .com registry is Verisign”. Now you can check what is the Nameserver of the example.com.
- Verisign: “example.com is currently using ns1.ezydomain.com and ns2.ezydomain.com as the nameserver”. Now you can check where is the website of example.com hosted at.
- You talk to Verisign again : “hey, can you give me the nameserver of ezydomain.com as well?”
- Verisign: “oh, ezydomain.com is using ns1.ezydomain.com as well. I will just give you the IP of ns1.ezydomain.com ’54.xxx.xxx.203′”
- 54.xxx.xxx.203: “You looking for the location of example.com? hmm, example.com having an A record that points to 41.xxx.xxx.105, please find the website you needed there”
- 41.xxx.xxx.105: “Here you go, this is the html file”
- You get the website and its resolved now!
Some of you may be smart and noticed why we need to register the nameserver with IP at the registry. When we trying to resolve a domain, we will lookup it’s NS as it is where the destination stored. Everything was fine until Step 4, however, when come to Step 5, the domain is using their own domain as the NS, if there isn’t any registered record for ns1.ezydomain.com, it will become forever loop on the Step 5.
In order to avoid such chaotic disaster, registries required the nameserver must be registered if it going to use on their own extension (.com NS using on .com domain).