What causes the “nRRPResponseCode 531” error, A fix to the nasty “nRRPResponseCode 531” error during domain name DNS change

Tuesday, 16th March 2010

For two days now, I’m trying to set a custom DNS server for a (.net) domain purchased by gigaspark.com . Every time I try to change the nameservers for the (.net) domain an irritating error pops up, the error reads “nRRPResponseCode 531” and I cannot set my custom configured Bind DNS server for the (.net) domain. I believe the same problem happens also with (.com) domains.

In this relation, I tried googling online searching and searching what might be the stupid cause of the “nRRPResponseCode 531” error that prevents me from setting my custom configured Bind domain name servers to mydomain.net . I also contacted the support team from gigaspark multiply until I found out what is the trouble cause.
In short the “nRRPresponseCode 531” is an error that indicates your .net or .com domain is not figuring in VeriSign’s GRS domain database .
The Verisign GRS domain database contains a list of DNS servers that are correctly configured and trustworthy enough. I’ve seen many people online suffering from the same terrible error,
who pointed out that the error is caused by misconfigurations in the Bind DNS server or the zone file for the problematic domain name, though I’ve looked through multiple times to possibly track the problem in both my major named.conf and the rest of bind’s configuration files as well as in the domain name I had registered mydomain.net ,there was nothing misconfigured or unusual.
I have to admit, this problem is really odd, because I was able to successfully set the same custom configured Bind DNS server for mydomain.info and mydomain.biz but, yet whenever trying to set the same Bind DNS for mydomain.net I came across the shitty nrRRPResponseCode 531 .
Thanks to the kind help of Gigaspark’s tech support together with some google posts on the matter I figured out Gigaspark are using ENOM – a major domain name registrar offering easy ways for an end domain providers to become their resellers.
It seems ENOM’s policy is enforces you as a domain name customer to register your full DNS domain name let’s say (ns1.mydns.com) in Verisign’s GRS domain database otherwise they refuse you the right to set yourself your ns1.mydns.com for your domain, because if the DNS domain name is not figuring in that database it’s not trust worthy!
I believe many people would agree with me this is a real shit! You pay for your domain and you should have the full rights over it.
I mean you should be allowed to set whatever DNS domain name even, if it’s not an existing one and they shouldn’t bother you with stupid DNS domain name registrations in stupid Verisign GRS databases and so on!
Now you probably wonder what is the required steps to take to be able to register the domain in that Verisign GRS database in order to be able to set your ns1.mydomain.com as a default DNS server for your mydomainname.com .
Well you have to contact your domain registrar, let’s say gigaspark.com .
You log to your account on tucowsdomains for your domain mydomain.com … then you find something similar to: “register a nameserver” among the overall menus options.
Then you have to register your nameserver ns1.mydomain.com. Then you wait between 24 up to 48h and then you have to test if your NS has already properly entered the Verisign GRS database you have to visit on Verisign GRS Whois .
Hopefully the guys from Verisign GRS would approve your DNS host to enter there database and then at last you might be able to set in your DNS host as a preferred DNS for your (.net) / (.com?) domain name.
So go back to gigaspark’s slovenian interface and try changing the DNSes once again! If you’re lucky with God’s help (for sure), you would be at last be successful in setting your BIND name server as a primary DNS.

Share this on:

Download PDFDownload PDF

Tags: , , , , , , , , ,

6 Responses to “What causes the “nRRPResponseCode 531” error, A fix to the nasty “nRRPResponseCode 531” error during domain name DNS change”

  1. Chris says:
    Firefox 3.6.3 Firefox 3.6.3 Mac OS X 10.6 Mac OS X 10.6
    Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv: Gecko/20100401 Firefox/3.6.3

    This is quite normal and I have been registering my name servers for years. Without name server registration the DNS system will not function. For example:

    Say I get a VPS and a domain name called example.com. I then configure example.com’s zone and set up your usual A record + CNAME + what have you and then I add an A record for ns1.example.com and ns2.example.com. At this stage I delegate example.com to ns1.example.com and ns2.example.com. The domain name will not function unless ns1.example.com and ns2.example.com are registered. All name servers should be registered.

    View CommentView Comment
    • Kevin says:
      Google Chrome 6.0.472.53 Google Chrome 6.0.472.53 Windows XP Windows XP
      Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/534.3 (KHTML, like Gecko) Chrome/6.0.472.53 Safari/534.3

      No, registration should only be required if you have your nameserver name set to something that is part of the domain you are trying to change it for.
      If I want to set my NS for blabla.com to ns1.example.com, it should work without the glue record.

      View CommentView Comment
      • Chris says:
        Google Chrome 6.0.472.63 Google Chrome 6.0.472.63 Windows XP Windows XP
        Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/534.3 (KHTML, like Gecko) Chrome/6.0.472.63 Safari/534.3

        Yes? All name server should be registered. If you were to use blabla.com with ns1.example.com etc it would work because they are already registered. I know this. I cannot see any fault in my reply. Please do not troll.

        View CommentView Comment
  2. admin says:
    IceWeasel 3.5.10 IceWeasel 3.5.10 GNU/Linux x64 GNU/Linux x64
    Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20100623 Iceweasel/3.5.10 (like Firefox/3.5.10)

    The solution to the whole mess finally. Was done by switching to Godaddy and using their options to select a certain domain name as a DNS domain name and later on use it for my DNS server.

    View CommentView Comment
  3. Ecarte Regeln says:
    Firefox 3.5.3 Firefox 3.5.3 Windows XP Windows XP
    Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv: Gecko/20090824 Firefox/3.5.3 (.NET CLR 3.5.30729)

    fabuleusa capara mi ralsiquia te cobida fario aclil. hetuzam te queirion boiario nos nafir o nhangi rabacurgu henfipto bien.

    View CommentView Comment
  4. Delmar Vasey says:
    Internet Explorer 7.0 Internet Explorer 7.0 Windows XP Windows XP
    Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30)

    Thanks for enabling me to attain new tips about pc’s. I also have the belief that certain of the best ways to help keep your laptop computer in best condition is to use a hard plastic material case, or maybe shell, that will fit over the top of your computer. A majority of these protective gear will be model unique since they are manufactured to fit perfectly above the natural outer shell. You can buy all of them directly from the seller, or from third party places if they are readily available for your laptop computer, however its not all laptop may have a shell on the market. All over again, thanks for your suggestions.

    View CommentView Comment

Leave a Reply

CommentLuv badge