Home / server / Questions / 147231
Accepted
danorton
Asked: 2010-06-02 11:51:31 +0800 CST

Why is the wrong name server information at crsnic.net & gtld-servers.net?

  • 772

Did I screw this up? I don’t even know how this might have happened, so I’d like to learn. I’m trying out HostGator’s reseller service and I bought a domain name through it, but I didn’t want the default name servers and so I changed them during the registration. After registration the domain name record is correct everywhere except at whois-servers.net and whois.crsnic.net and it looks like the DNS network is using that same information.

$ whois -h whois.enom.com. example.com
...
Name Servers:
   dns1.name-services.com
   dns2.name-services.com
   dns3.name-services.com
   dns4.name-services.com
   dns5.name-services.com
...
$ whois -h whois.crsnic.net. example.com
   Domain Name: EXAMPLE.COM
   Registrar: ENOM, INC.
   Whois Server: whois.enom.com
   Referral URL: http://www.enom.com
   Name Server: NS1.HOSTGATOR.COM
   Name Server: NS2.HOSTGATOR.COM
   Status: clientTransferProhibited
   Updated Date: 01-jun-2010
   Creation Date: 31-may-2010
   Expiration Date: 31-may-2011

>>> Last update of whois database: Tue, 01 Jun 2010 19:20:47 UTC <<<
...
    $ dig +norecurse @b.gtld-servers.net. example.com. NS
...
;; AUTHORITY SECTION:
example.com.      172763  IN      NS      ns2.hostgator.com.
example.com.      172763  IN      NS      ns1.hostgator.com.
...

My next step is to let HostGator have a look, but first I want to better understand how this happened.

Thanks.

domain-name-system domain-registration domain-name domain-registrar

2 Answers

  1. Best Answer

    I would contact the registrar to ensure they actually pushed the change out to the root DNS servers and have the correct information on file. I haven't used HostGator specifically, but some of the registrar APIs that I've had to talk to in the past have been.... glitchy.

    • 0

  2. The way it’s supposed to work is that when you update registration information for .COM, .NET, and .EDU domain names, the registrar should send the the new WHOIS information to CRSNIC. The problematic situation described above is one possible result when that transfer fails.

    While it’s arguable that CRSNIC might have dropped the ball somewhere, eNom could have automatically checked to confirm that the CRSNIC record had been updated, and obviously didn’t.

    I would conclude that eNom failed to properly transfer (and confirm the transfer of) the updated WHOIS name server information to CRSNIC.

    • -1