I have several domains registered with godaddy for various clients. One of the domains' websites went down, so I investigated...
www.domain.dom was down, so I started at the beginning:
dig +short domain.dom NS
ns43.domaincontrol.com.
ns44.domaincontrol.com.
Ok, so let's see if they're responding correctly:
dig
www.domain.dom @ns43.domaincontrol.com.
; <<>> DiG 9.3.4 <<>>
www.domain.dom @ns43.domaincontrol.com
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 1757
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;
www.domain.dom. IN A
;; AUTHORITY SECTION:
domain.dom. 86400 IN SOA ns43.domaincontrol.com. dns.jomax.net. 2007081000 28800 7200 604800 86400
;; Query time: 37 msec
;; SERVER: 208.109.78.180#53(208.109.78.180)
;; WHEN: Tue Oct 30 15:12:00 2007
;; MSG SIZE rcvd: 103
UH OH!
dig
www.domain.dom @ns44.domaincontrol.com.
; <<>> DiG 9.3.4 <<>>
www.domain.dom @ns44.domaincontrol.com
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 35203
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;
www.domain.dom. IN A
;; AUTHORITY SECTION:
domain.dom. 86400 IN SOA ns43.domaincontrol.com. dns.jomax.net. 2007081000 28800 7200 604800 86400
;; Query time: 38 msec
;; SERVER: 208.109.80.75#53(208.109.80.75)
;; WHEN: Tue Oct 30 15:12:25 2007
;; MSG SIZE rcvd: 103
****; not good - better check if everything is still set up correctly. I haven't logged into GoDaddy in at least a month; there's no reason this should suddenly not be working.
Sure enough, everything seems normal.
Default Hosting Nameservers (NS43.DOMAINCONTROL.COM, NS44.DOMAINCONTROL.COM)
Whois confirms this information.
So I call Go Daddy and spend half an hour on the phone with someone there. He doesn't know much about DNS; he thinks that web browsers do whois queries to find out where a website is!
He's unable to understand the problem. He finally suggests I switch from using their hosting nameservers to their parked nameservers, but can't provide an explanation for why doing so should fix the problem.
The guidance on that page is not helpful:
If your domain(s) are hosted here, choose 'Default Hosting Nameservers.'
If your domain(s) are parked here, choose 'Default Parked Nameservers.'
If your domain(s) are hosted somewhere else, choose 'Custom Nameservers.'
Default Hosting Nameservers (NS43.DOMAINCONTROL.COM, NS44.DOMAINCONTROL.COM)
Default Parked Nameservers (NS05.DOMAINCONTROL.COM, NS06.DOMAINCONTROL.COM)
Custom Nameservers
I want to continue doing what I've done for years: use their nameservers, but not use their hosting, or park the domains either. I want to continue to host the site at another IP, where I have a working web server set up; it hasn't changed in months either.
In the (mis-named) total dns control, there's still an A record for the webserver I use.
Why they decided to break this and screw up their customers is beyond me. I'm tired of them.
If you wish to verify the information provided, please feel free to contact me for the domain name in question.
Linear Mode
