nslookup failure ns01.domaincontrol.com
pbob said 2 years, 1 month ago:
Really odd thing happened today – I have bind9 running on a local machine. Suddenly, ns01.domaincontrol.com and ns02.domaincontrol.com started giving me unexpected RCODE REFUSED failures on my goDaddy-hosted accounts (nothing has changed anywhere for months).
nslookup myDomainName ns01.domaincontrol.com fails
nslookup myDomainName ns02.domaincontrol.com fails
nslookup myDomainName 8.8.8.8 succeeds.
nslookup anythingElseOnThePlanet succeeds.
nslookup anyDomainNameServedByns01 ns01.domaincontrol.com fails
Samething happens if I use ns02.domaincontrol.com. ns01 and ns02 are the name servers for my domain name.
Again, the only thing that I have found that my local machine will NOT lookup is anything served by ns01 or ns02 – the local machine will lookup everything else on the planet. I did a web search, found a couple more domain names served by ns01 and ns02 – and nslookup thoseDomainNames ns01.domaincontrol.com fail as well.
Any ideas?
steves said 2 years, 1 month ago:
@pbob
We are not having any issue with these nameservers at the moment. You may want to do a flush dns to see if that resolves the issue. Otherwise, if you could reply back with your domain and whether or not your domains are resolving. If they are not a trace route would also help.
Thanks.
-Steve
chucko6166 said 2 years, 1 month ago:
I respectfully submit that you ARE having problems with ns01.domaincontrol and ns02.domaincontrol.com.
One of the sites that I manage is affected by the ability to resolve the domain properly.
I see this from NSlookup:
server ns01.domaincontrol.com
Default Server: ns01.domaincontrol.com
Address: 216.69.185.1
>premach.com
Server: ns01.domaincontrol.com
Address: 216.69.185.1
*** ns01.domaincontrol.com can’t find premach.com: Query refused
and there are others reporting the problem:
his most recent post and the third post speak to the issue.
I just wasted over an hour on the phone with one of your support techs. He kept wanting me to run a tracert to the domain name and I kept telling him that if the domain won’t resolve properly that a tracert to the domain won’t work. I did run a tracert to the IP address of the website and it did complete properly (20 hops). 5 minutes later he wanted me again to run a tracert to the domain name.
I sent screen caps of the nslookup and offered to talk directly to the higher level support techs but he said that was not possible.
It’s simple folks – get this fixed. It’s not our job to teach your tech support folks how this stuff works. Don’t waste our time and be responsive and genuinely interested in solving the problems and you’ll keep us as a customer. Give us the runaround and waste our time and we’ll be forced to go elsewhere.
You choose.
pbob said 2 years, 1 month ago:
Steves – thanks for the reply and any help you can provide here….
My domain name will resolve via external resolvers… but anything that is served by ns01.domaincontrol.com and ns02.domaincontrol.com will not resolve from my local machine running bind9… I have cleared cache’s and waited 24 hours (all cache’s should be cleared by then) – and still same thing.
For example:
nslookup monova.org 8.8.8.8
Server: 8.8.8.8
Address: 8.8.8.8#53
Non-authoritative answer:
Name: monova.org
Address: 74.113.68.18
nslookup monova.org ns02.domaincontrol.com
Server: ns02.domaincontrol.com
Address: 208.109.255.1#53
** server can’t find monova.org: REFUSED
Here is the traceroute – it hangs somewhere in level 3′s network (note I can ping both domain servers ns01 and ns02).
traceroute to ns01.domaincontrol.com (216.69.185.1), 30 hops max, 60 byte packets
1 174.52.96.1 (174.52.96.1) 22.954 ms 23.889 ms 29.758 ms
2 te-3-3-ur07.saltlakecity.ut.utah.comcast.net (68.87.220.245) 15.273 ms 15.530 ms 15.747 ms
3 te-3-1-ar01.saltlakecity.ut.utah.comcast.net (68.86.199.149) 15.391 ms 15.613 ms 16.188 ms
4 te-9-3-ar02.saltlakecity.ut.utah.comcast.net (68.87.170.6) 15.816 ms 16.301 ms 16.409 ms
5 te-0-0-0-1-cr01.denver.co.ibone.comcast.net (68.86.90.133) 27.690 ms 28.629 ms 28.748 ms
6 4.28.20.5 (4.28.20.5) 59.648 ms 45.249 ms 45.249 ms
7 ae-32-52.ebr2.Denver1.Level3.net (4.69.147.109) 26.438 ms 25.346 ms 28.941 ms
8 ae-3-3.ebr1.Chicago2.Level3.net (4.69.132.62) 53.157 ms 53.800 ms 53.801 ms
9 ae-1-100.ebr2.Chicago2.Level3.net (4.69.132.114) 53.804 ms 47.075 ms 50.597 ms
10 ae-6-6.ebr2.Washington12.Level3.net (4.69.148.145) 78.610 ms 79.595 ms 79.743 ms
11 ae-5-5.ebr2.Washington1.Level3.net (4.69.143.221) 80.673 ms 80.078 ms 80.523 ms
12 ae-62-62.csw1.Washington1.Level3.net (4.69.134.146) 79.927 ms ae-72-72.csw2.Washington1.Level3.net (4.69.134.150) 80.742 ms ae-82-82.csw3.Washington1.Level3.net (4.69.134.154) 79.791 ms
13 ae-24-70.car4.Washington1.Level3.net (4.69.149.70) 80.838 ms ae-34-80.car4.Washington1.Level3.net (4.69.149.134) 80.945 ms ae-24-70.car4.Washington1.Level3.net (4.69.149.70) 85.740 ms
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
chucko6166 said 2 years, 1 month ago:
This morning ns01.domaincontrol.com is still refusing connections but ns02.domaincontrol is answering.
Here is output from dig queries that I performed a few minutes ago:
First, ns01.domaincontrol.com
; <<>> DiG 9.3.2 <<>> premach.com @ns01.domaincontrol.com
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 1544
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;premach.com. IN A
;; Query time: 109 msec
;; SERVER: 216.69.185.1#53(216.69.185.1)
;; WHEN: Mon Apr 11 06:18:57 2011
;; MSG SIZE rcvd: 29
and ns02.domaincontrol.com
; <<>> DiG 9.3.2 <<>> premach.com @ns02.domaincontrol.com
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1529
;; flags: qr aa; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0
;; QUESTION SECTION:
;premach.com. IN A
;; ANSWER SECTION:
premach.com. 3600 IN A 184.168.237.1
;; AUTHORITY SECTION:
premach.com. 3600 IN NS ns01.domaincontrol.com.
premach.com. 3600 IN NS ns02.domaincontrol.com.
;; Query time: 109 msec
;; SERVER: 208.109.255.1#53(208.109.255.1)
;; WHEN: Mon Apr 11 06:19:39 2011
;; MSG SIZE rcvd: 97
chucko6166 said 2 years, 1 month ago:
ns01.domaincontrol.com still refusing connections.
ns02.domaincontrol.com still responding correctly.
dig queries exactly as I posted them 12 hours ago.
chucko6166 said 2 years, 1 month ago:
It’s now been several days since this problem was first reported, and it is still unresolved.
ns01.domaincontrol.com still refuses connections, as indicated in the Dig queries that I posted earlier.
ns02.domaincontrol.com does answer correctly.
I doublechecked these responses with another DIG query to each a few minutes ago.
I’m not the only one reporting this problem.
See here for more information:
Does anyone from GoDaddy even read these forums?
Can someone from GoDaddy please respond and tell us when this is going to be fixed?
chucko6166 said 2 years, 1 month ago:
It looks like this problem has been around for a while:
http://support.godaddy.com/groups/domains-management-and-services/forum/topic/dns-issues/
Where is tech support?
0 min expected wait time