Hi,
So this started a little while ago but seems to be getting worse.
What I am seeing is dns servers over at godaddy not replying however I seem to be able to traceroute ok to them. Also I have started to see that the whois.godaddy.com servers also seem to be having issues as well with "Whois information is currently unavailable. Please try again later."
Anyone else also seeing issues this morning? And able to confirm the issue is with godaddy?
Sincerely,
Do you have any particular NSes and/or domains we can test with?
I've seen reports of this for a week or so, with the symptoms looking like overly aggressive abuse / query rate handling - packets from networks containing busy resolvers being blocked.
Grapevine tells me that they don't think they're doing it intentionally (maybe they outsourced something and it broke?).
Cheers,
Steve
a few hours ago... One of my MX gateway filtering clients (for the small
spam filtering portion of my business) was having trouble this morning
with their own users accessing webmail (hosted on their exchange
server), and I discovered that the "a" record was resolving from some
locations, but not from others. The domain was using GoDaddy's
"domaincontrol.com" series of name servers. I thought that they might
have had wrong host names in their registrar records and I told my
client to contact Godaddy, verify that these were correct, and ask
Godaddy about possible timeout and/or "no answer" issues. I tried
querying the host name from one location (direct to Godaddy's DNS) and
I'd get an answer, then from another location (direct to Godaddy's DNS)
and I would get a seemingly endless timeout.
Hi,
They all came back later and are good now. But next time if it happens I will send some of the NS servers and domains.
Sincerely,
Mark
The following nameservers for godaddy.com are currently down. The
machines themselves are up as we can ping them.
godaddy.com. @2600:1403:a::43 (a8-67.akam.net.): dns=timeout edns=timeout edns1=timeout edns@512=timeout ednsopt=timeout edns1opt=timeout
godaddy.com. @2a02:26f0:67::41 (a20-65.akam.net.): dns=timeout edns=timeout edns1=timeout edns@512=timeout ednsopt=timeout edns1opt=timeout
godaddy.com. @2600:1401:1::42 (a6-66.akam.net.): dns=timeout edns=timeout edns1=timeout edns@512=timeout ednsopt=timeout edns1opt=timeout
The above was from EDNS compliance testing I am doing. The report
is regenerated daily.
I have an ear to whisper in on this topic at GD.
If you're still having trouble through today, Thursday, please reply
on this thread (or, if you're on Outages@, preferably over on that thread),
with what, when, and how, and I will pass the hard data along.
If you've already posted details here, just confirm still a problem, and
I can harvest.
The majority of the trouble is layer 3 and above, as I understand it;
ping/trace to the relevant servers is working on, generally? If otherwise,
mention that as well, pse.
Cheers,
-- jra