Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I'm trying to change nameservers for some of my domains at GoDaddy, but I occasionally run into "Nameserver not registered" problems, and then I'm not allowed to set the nameservers. Here are the cases I've tried, and I still don't understand what it takes to have a registered nameserver.

With ns1 and ns2 pointing to my nameservers, I can set the nameservers successfully when I set up domains as follows:

Host Summary entries for ns1 and ns2 at GoDaddy
.co.cc domains with A records for ONLY ns1 and ns2
Hosted with other nameservers. Have only A records for ns1 and ns2

But these do NOT work (nameserver not registered error):

.info domains at GoDaddy with A records for ONLY ns1 and ns2
Hosts with dyndns.org that point to IP of nameservers

Also, when I dig any domains hosted at my nameservers using any of the above, I get the correct response. So what's the deal here? Why do the last two cases get "nameserver not registered errors"? Thanks!

share|improve this question

1 Answer 1

up vote 6 down vote accepted

Log into the godaddy.com portal and edit the domain you want to change the DNS settings for (You are looking for the domain Manager).

In the host summary (bottom left) is where you need to add the entries to ns1 and ns2 along with their IP addresses.

It'll then take a little bit for everything to replicate so that you can point other domains to those names.

share|improve this answer
    
I know that. I was wondering why I -have- to do that in GoDaddy when I can just use A records in other areas. And overall what technically labels a nameserver as "registered". But thanks, +1 because you'll help others figure out how to solve this problem in the first place. –  Lin Sep 1 '09 at 7:07
4  
They need this specified to ensure that they always know where your DNS servers are. If you own company.com, and you tell them that your name server is ns1.company.com, they have no idea of knowing what the IP address is for ns1.company.com because an nslookup for ns1.company.com will fail because they don't have the IP address to get to ns1.company.com. It's your classic "what came first, the chicken or the egg" situation. –  mrdenny Sep 1 '09 at 7:36

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.