nRRPResponseCode 531 Name Server Error
Published January 6th, 2008 in Tech-RamblingThis is an excellent example of me being an idiot. I have pretty much made the decision to go from Dreamhost to Slicehost, so I thought I would start by transferring my least-used domain as the guinea pig. I created all the DNS records per the nice tutorial and proceeded to change the name servers at my registrar (in this case, namecheap.com). Each time I tried, the response was “nRRPResponseCode 531″ and nothing else.
Somehow my knowledge of the English language did not interpret “nRRPResponseCode 531″ to mean anything to me, so I hopped over to my buddy Google and proceeded to waste a lot of time. I found that this means the name servers are not valid and little else. After a lot more time, I eventually realized that I am an idiot. The nameservers at Slicehost are ns{1,2,3}.slicehost.net and I had done “.com” at the registrar.
If you’re having this same problem, make sure you have all the DNS records set up and then use the correct name servers, lol.
Thanks! I had this same problem for the same reason. Thanks for your help.
Glad I could help more than the cryptic “nRRPResponseCode 531″ response
you are a genius … i wasted about 40 minutes before coming to this post haha!
oh god…I wasted a hell of a lot more than 40 minutes with this, I’ll tell you that.
thanks a lot
Just done the same thing, thanks for posting possibly saved me hours
Faulty spelling / names are just one of the issues for which you might receive a 531 error. You might see the error if:
(a) the nameservers are genuinely faulty as in not properly setup in which case, you need to contact the dud that gave you the nameserver details.
(b) the nameservers are not yet registered at the domain registery (it usually takes 4 to 5 days to complete the process)
For the technically inclined, there is some nice bed-time reading material here:
http://www.tech-faq.com/reverse-dns.shtml