We're starting to see errors with Go Daddy DNS. Is anyone else experiencing issues?
-J
We noticed some issues to Google & Level3 DNS last night:
8.8.8.8
8.8.4.4
4.2.2.2
1/23/14 00:55:17 - 00:55:47 (UTC-5)
1/23/14 01:09:32 - 01:11:03 (UTC-5)
Have not yet determined if it was a local carrier issue.
Someone on outages@outages.org reported issues getting to eBay / Paypal IP's
at roughly the same time.
I wonder if there was a general brief carrier issue last night.
always helps to have examples of the problems... ie:
I did - dig www.godaddy.com @8.8.8.8
I expected:
;; QUESTION SECTION:
;www.godaddy.com. IN A
;; ANSWER SECTION:
www.godaddy.com. 29 IN CNAME www.godaddy.com.edgekey.net.
www.godaddy.com.edgekey.net. 550 IN CNAME e8804.a.akamaiedge.net.
e8804.a.akamaiedge.net. 14 IN A 23.79.77.116
but I got:
;; QUESTION SECTION:
;www.godaddy.com. IN A
www.godaddy.com. 14 IN A zippidy-doo.com!.
I made my query from the north-east elbonian region of youville.
-chris
We noticed some issues to Google & Level3 DNS last night:
8.8.8.8
8.8.4.4
4.2.2.21/23/14 00:55:17 - 00:55:47 (UTC-5)
1/23/14 01:09:32 - 01:11:03 (UTC-5)Have not yet determined if it was a local carrier issue.
Someone on outages@outages.org reported issues getting to eBay / Paypal IP's
at roughly the same time.I wonder if there was a general brief carrier issue last night.
From: Jason [mailto:Jason@viviotech.net]
Sent: Thursday, January 23, 2014 3:57 AM
To: nanog@nanog.org
Subject: GoDaddy DNSWe're starting to see errors with Go Daddy DNS. Is anyone else experiencing
issues?always helps to have examples of the problems... ie:
I did - dig www.godaddy.com @8.8.8.8
I expected:;; QUESTION SECTION:
;www.godaddy.com. IN A
;; ANSWER SECTION:
www.godaddy.com. 29 IN CNAME www.godaddy.com.edgekey.net.
www.godaddy.com.edgekey.net. 550 IN CNAME e8804.a.akamaiedge.net.
e8804.a.akamaiedge.net. 14 IN A 23.79.77.116but I got:
;; QUESTION SECTION:
;www.godaddy.com. IN A
www.godaddy.com. 14 IN A zippidy-doo.com!.
I should be clear that there are no bangs (!) in dns.... so this above
is clearly fictious dig output (the first instance is actual output...
I was lazy and copy/pasted edited the output.
I made my query from the north-east elbonian region of youville.
also, there is no elbonia... there may be a youville though, and i'm
sorry for slurring the youville inhabitants with the stink of elbonia
You sure? Over the years, I've dealt with a lot of gear designed and built there.
Hell; all of China's traffic got mysteriously routed there last week...
Cheers,
-- jra
This has been going on off and on for a while.
Todd
I should be clear that there are no bangs (!) in dns.
the dns is 8-bit clean. bangs, dots (not as separators), blanks, etc.
are all valid. some applications may have trouble with use of some of
these 
randy
> I should be clear that there are no bangs (!) in dns.
the dns is 8-bit clean. bangs, dots (not as separators), blanks, etc.
are all valid. some applications may have trouble with use of some of
these
Not in the right-hand side (RDATA portion) of a type A record.
The 32 bits will be interpreted as the bits of an IPv4 address, which are
always 4 numeric values (0 to 255) separated by dots.
"www.godaddy.com. 14 IN A zippidty-doo.com!"
Is right out.
If it were a "HS TXT", CH TXT, IN TXT, IN CNAME, IN NS, IN MX, IN SRV,
or other similar fields, then sure.
Well, that's how they're listed in master files, anyway; that's the
only constraint RFC 1035 makes (see section 3.4.1). If you're
outputting them for human consumption, you could of course output them
in some other format. That might be surprising to some. (It's sure
not what dig does.) I have heard claims that some hosts on the
Internet did use other representations of v4 addresses for human
consumption. I have never observed this. Certainly, the wire format
is not dotted-quad, of course.
(None of this is to disagree that anything other than a 32 bit
Internet address would be ill-formed RDATA for an A record.)
A