I entered nameservers for a domain that I have at directNIC and got this error message: "Sorry, Nameserver 1 is not a registered nameserver" .

However, I know the name servers are OK.
- I tried the same nameservers with a domain that I have with Namecheap and it took it just fine.
- I pinged the nameservers and they responded just fine.
- I also checked with the host, and they claim everything is up and running just fine.

I've submitted a trouble ticket with directNIC, but it's been a few hours and I still haven't heard from them. Perhaps their stumped? Why would this work on one registrar and not on another? Strange!

Does anyone have a clue as to what the problem might be? I'm checking this out as a favor to a friend who bought a domain on directNIC (from my recommendation) and was unable to set his nameservers. He got the same message I'm getting.

Your problem is not really a configuration problem, it is more that your server is not really REGISTERED in any nameservers directory.

You do not mention who is the domain's registrar, but you should go to it and look at their FAQs to see how to register your nameservers with them. Go Daddy, for instance, allows to do this if you bought a domain with them, and I guess most registrars will do the same.

Once the server is registered, then it's only a configuration problem. A good site is http://www.dnsreport.com to check your configuration.

but if they are an openSRS reseller here is the problem. From OpenSRS tech support.

Hello,

Most Registries keep their own list of valid nameservers. Each Nameserver host record must be added before it can be used.

RSPs can now do this via "Registry Nameservers" on the Resellers web page.

IP addresses are not required by the registry and are not displayed by our system. This does not affect the operation of the nameserver.

Hope this helps

Robert Rivers
OpenSRS Technical Operations


I had the same problem trying to move a clients domain to my servers and danced around for 3 weeks with the register till I got pissed and contacted OpenSRS myself. Once I copied him the email it was done in an hour.

I really think he didn't know he had to add them to his list.

Monte

directNIC replied to me and said that everything should work OK now. However, when I tried it again, it still didn't work. Something strange is going on.

Originally posted by Wismie
Your problem is not really a configuration problem, it is more that your server is not really REGISTERED in any nameservers directory. Well, what's weird is that the nameservers work when I try them with a domain name that I have with Namecheap, but with directNIC they don't work. The nameservers aren't the same as the domain name. The nameservers are registered to the host, and as I said, they seem OK with Namecheap.

Once the server is registered, then it's only a configuration problem. A good site is http://www.dnsreport.com to check your configuration. Nice site! Thanks. I tried the domain name of the host and it returns the expected nameservers.

Originally posted by Monte
Most Registries keep their own list of valid nameservers. Each Nameserver host record must be added before it can be used.
Hmm. Well, since directNIC told me that it should work now, perhaps that's what they did - add the nameserver to their list of registries. But since it still didn't work, perhaps there is some time delay - propagation?

What's weird is that I've registered my own name server and I host it on my ded server. I've never had any trouble, ever, using my nameserver, no matter which registrar or domain name. Go figure.

Strange??? Sorry, I have all my domains with the registrar mentioned above (:cartman: ) and never had any problem. So if I understand well, one of your registrar does recognizes your nameservers, and not the other one?

Originally posted by Wismie
Strange??? Sorry, I have all my domains with the registrar mentioned above (:cartman: ) and never had any problem. So if I understand well, one of your registrar does recognizes your nameservers, and not the other one? Correct. eNom recognizes the nameservers, but directNIC returns an error stating that the nameserves are not registered.This is driving me crazy.

How long ago did you register the nameservers, by the sound of things it was fairly recent (last day or so)? If so then you need to let the dns propogate before you can use them for accounts, as the DNS won't show up in all the registries right away. The DNS hasn't fully propogated because one of the registries cannot find that NS info.

HTH
Steven

Originally posted by insiderhosting
How long ago did you register the nameservers, by the sound of things it was fairly recent (last day or so)? If so then you need to let the dns propogate before you can use them for accounts, as the DNS won't show up in all the registries right away. The DNS hasn't fully propogated because one of the registries cannot find that NS info. These aren't my nameservers, these are the host's nameservers, already in use for quite some time. And as I said in my first post, it's recognized by another registrar (enom), just not by directNIC.

One strange thing I just noticed... When I misspelled the name of the nameserver DSN.nameserver.com and not DNS.nameserver.com, it was accepted with no error. Am I in need of therapy?

A remote possibility occurs to me. Are you /your host registering 2 nameservers with the same IP [I mean dns.yourdomain.com - 1.2.3.4 and dns.hisdomain.com 1.2.3.4]?

If the registrar does a reverse look up this could occur

Just a wild thought

Cheers
Balaji