Google Public DNS Problems?

Is anyone else seeing this? From Santa Clara, CA, on Comcast Business...I'm getting SERVFAIL for any query I throw at 8.8.8.8 and 8.8.4.4... Level 3's own public resolvers are fine for me, as are OpenDNS's resolvers. Blair

Re: Google Public DNS Problems?

Works fine from here, Philadelphia, PA .edu and FIOS networks Cheers, Harry On 05/01/2013 12:09 PM, Blair Trosper wrote: > Is anyone else seeing this? From Santa Clara, CA, on Comcast > Business...I'm getting SERVFAIL for any query I throw at 8.8.8.8 and > 8.8.4.4... > > Level 3's own public re

Re: Google Public DNS Problems?

On 2013-05-01, at 12:09, Blair Trosper wrote: > Is anyone else seeing this? From Santa Clara, CA, on Comcast > Business...I'm getting SERVFAIL for any query I throw at 8.8.8.8 and > 8.8.4.4... > > Level 3's own public resolvers are fine for me, as are OpenDNS's resolvers. Google just turned o

Re: Google Public DNS Problems?

That's all well and good, but I certainly wouldn't expect "nslookup gmail.com" or for "nslookup google.com" to return SERVFAIL On Wed, May 1, 2013 at 9:34 AM, Joe Abley wrote: > > On 2013-05-01, at 12:09, Blair Trosper wrote: > > > Is anyone else seeing this? From Santa Clara, CA, on Comcast

Re: Google Public DNS Problems?

No issues on Comcast cable in the bay area, either Comcast business or Comcast home. Scott $ nslookup gmail.com 8.8.4.4 Server: 8.8.4.4 Address:8.8.4.4#53 Non-authoritative answer: Name: gmail.com Address: 74.125.239.149 Name: gmail.com Address: 74.125.239.150 On Wed,

Re: Google Public DNS Problems?

On Wed, May 1, 2013 at 9:38 AM, Blair Trosper wrote: > That's all well and good, but I certainly wouldn't expect "nslookup > gmail.com" or for "nslookup google.com" to return SERVFAIL > If you set the CD (checking disabled) in the request, a response that would normally be SERVFAIL due to DNSSEC

Re: Google Public DNS Problems?

Goes all the way up to the A root server before failing spectacularly. Europa:~ blair$ dig +cd @8.8.8.8 google.com A ; <<>> DiG 9.8.3-P1 <<>> +cd @8.8.8.8 google.com A ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 47332 ;; flags: qr

Re: Google Public DNS Problems?

8.8.4.4 is now replying SERVFAIL whereas 8.8.8.8 is suddenly working fine again... On Wed, May 1, 2013 at 10:07 AM, Blair Trosper wrote: > Goes all the way up to the A root server before failing spectacularly. > > Europa:~ blair$ dig +cd @8.8.8.8 google.com A > > ; <<>> DiG 9.8.3-P1 <<>> +cd @8.

Re: Google Public DNS Problems?

Your IPs may have been rate limited... Andy Andrew Fried andrew.fr...@gmail.com On 5/1/13 12:38 PM, Blair Trosper wrote: > That's all well and good, but I certainly wouldn't expect "nslookup > gmail.com" or for "nslookup google.com" to return SERVFAIL > > > On Wed, May 1, 2013 at 9:34 AM, Joe

Re: Google Public DNS Problems?

Blair Trosper wrote: > Goes all the way up to the A root server before failing spectacularly. That is an extremely weird response. Are you sure your queries are not being intercepted by a middlebox? What happens if you use dig +vc ? Do you get a similar round-trip time when pinging 8.8.8.8 to th

Re: Google Public DNS Problems?

Once upon a time, Joe Abley said: > Raw output from dig/drill and traceroutes to 8.8.8.8/8.8.4.4 are highly > recommended if you need to take this further. Does Google (and OpenDNS for that matter) support any "special" queries that identify the host/cluster/etc.? Something like BIND's CHAOS HO

Re: Google Public DNS Problems?

On May 1, 2013, at 1:39 PM, Tony Finch wrote: > Blair Trosper wrote: > >> Goes all the way up to the A root server before failing spectacularly. > > That is an extremely weird response. Are you sure your queries are not > being intercepted by a middlebox? What happens if you use dig +vc ? > D

Re: Google Public DNS Problems?

Traceroute is getting the right place and 8.8.8.8 is working, though :) On Wed, May 1, 2013 at 11:23 AM, Jared Mauch wrote: > > On May 1, 2013, at 1:39 PM, Tony Finch wrote: > > > Blair Trosper wrote: > > > >> Goes all the way up to the A root server before failing spectacularly. > > > > Tha

Re: Google Public DNS Problems?

On 5/1/13 2:23 PM, "Jared Mauch" wrote: >On May 1, 2013, at 1:39 PM, Tony Finch wrote: >>Blair Trosper wrote: >> >>> Goes all the way up to the A root server before failing spectacularly. >> >> That is an extremely weird response. Are you sure your queries are not >> being intercepted by a mi

Re: Google Public DNS Problems?

It is very courteous to reply a SERVFAIL for requests being rate limited. On Wed, May 1, 2013 at 1:17 PM, Andrew Fried wrote: > Your IPs may have been rate limited... > > Andy > > Andrew Fried > andrew.fr...@gmail.com > > On 5/1/13 12:38 PM, Blair Trosper wrote: >> That's all well and good, but I

Re: Google Public DNS Problems?

On Wed, May 1, 2013 at 4:14 PM, Yang Yu wrote: > It is very courteous to reply a SERVFAIL for requests being rate limited. > > I believe the 'rate-limit' response is actually 'no response' ... though I haven't tested this myself :) > On Wed, May 1, 2013 at 1:17 PM, Andrew Fried > wrote: > > Yo

Re: Google Public DNS Problems?

On May 1, 2013 5:09 PM, "Christopher Morrow" wrote: > > On Wed, May 1, 2013 at 4:14 PM, Yang Yu wrote: > > > It is very courteous to reply a SERVFAIL for requests being rate limited. > > > > > I believe the 'rate-limit' response is actually 'no response' ... though I > haven't tested this myself

Re: Google Public DNS Problems?

On 5/1/13 12:38 PM, Blair Trosper wrote: > That's all well and good, but I certainly wouldn't expect "nslookup > gmail.com " or for "nslookup google.com" to return > SERVFAIL > > Do you have traceroutes to 8.8.8.8 and 8.8.4.4?

Re: Google Public DNS Problems?

- Original Message - > From: "Perry Lorier" > On 5/1/13 12:38 PM, Blair Trosper wrote: > > > That's all well and good, but I certainly wouldn't expect "nslookup > > gmail.com " or for "nslookup google.com" to return > > SERVFAIL > Do you have traceroutes to 8.8.8.8 and

Re: Google Public DNS Problems?

On Thu, May 2, 2013 at 10:32 AM, Jay Ashworth wrote: > - Original Message - > > From: "Perry Lorier" > > > On 5/1/13 12:38 PM, Blair Trosper wrote: > > > > > That's all well and good, but I certainly wouldn't expect "nslookup > > > gmail.com " or for "nslookup google.co

Re: Google Public DNS Problems?

- Original Message - > From: "Christopher Morrow" > On Thu, May 2, 2013 at 10:32 AM, Jay Ashworth wrote: > > > - Original Message - > > > From: "Perry Lorier" > > > > > On 5/1/13 12:38 PM, Blair Trosper wrote: > > > > > > > That's all well and good, but I certainly wouldn't exp

Re: Google Public DNS Problems?

On 2013-05-02, at 11:51, Jay Ashworth wrote: > But since Perry's problem is *inability to resolve names in google's > public zones*, the *path to the ZONE servers* is the thing diagnostics > would require a trace to, no? Blair's problem, I think. Perry was just being helpful. Blair's point was

Re: Google Public DNS Problems?

Joe, That's not entirely true.You can easily do lookup for whoami.akamai.net and it will return the unicast address for the node in question (provided the local resolver is able to do the resolution).This is a frequent lookup that I do when I don't know what actual anycast node I'm us

Re: Google Public DNS Problems?

On Thu, May 2, 2013 at 11:51 AM, Jay Ashworth wrote: > - Original Message - > > From: "Christopher Morrow" > > > On Thu, May 2, 2013 at 10:32 AM, Jay Ashworth wrote: > > > > > - Original Message - > > > > From: "Perry Lorier" > > > > > > > On 5/1/13 12:38 PM, Blair Trosper wrot

Re: Google Public DNS Problems?

On 2013-05-02, at 11:59, Charles Gucker wrote: > That's not entirely true.You can easily do lookup for > whoami.akamai.net and it will return the unicast address for the node > in question (provided the local resolver is able to do the > resolution).This is a frequent lookup that I d

Re: Google Public DNS Problems?

On 2013-05-02, at 12:10, Joe Abley wrote: > On 2013-05-02, at 11:59, Charles Gucker wrote: > >>That's not entirely true.You can easily do lookup for >> whoami.akamai.net and it will return the unicast address for the node >> in question (provided the local resolver is able to do the >>

whoami.akamai.net [was: Google Public DNS Problems?]

On May 02, 2013, at 12:12 , Joe Abley wrote: > On 2013-05-02, at 12:10, Joe Abley wrote: >> On 2013-05-02, at 11:59, Charles Gucker wrote: >>> That's not entirely true.You can easily do lookup for >>> whoami.akamai.net and it will return the unicast address for the node >>> in question (p

Re: whoami.akamai.net [was: Google Public DNS Problems?]

On 2 May 2013 11:12, Patrick W. Gilmore wrote: > On May 02, 2013, at 12:12 , Joe Abley wrote: >> On 2013-05-02, at 12:10, Joe Abley wrote: >>> On 2013-05-02, at 11:59, Charles Gucker wrote: > That's not entirely true.You can easily do lookup for whoami.akamai.net and it will ret

Re: whoami.akamai.net [was: Google Public DNS Problems?]

On May 02, 2013, at 14:42 , "Constantine A. Murenin" wrote: > On 2 May 2013 11:12, Patrick W. Gilmore wrote: >> For clarity: Looking up the hostname "whoami.akamai.net" will return the IP >> address in the source field of the packet (DNS query) which reached the >> authoritative name server fo

Re: whoami.akamai.net [was: Google Public DNS Problems?]

On Thu, May 2, 2013 at 2:12 PM, Patrick W. Gilmore wrote: > On May 02, 2013, at 12:12 , Joe Abley wrote: > > On 2013-05-02, at 12:10, Joe Abley wrote: > >> On 2013-05-02, at 11:59, Charles Gucker wrote: > > >>> That's not entirely true.You can easily do lookup for > >>> whoami.akamai.net

Re: whoami.akamai.net [was: Google Public DNS Problems?]

On 2013-05-03 4:57 am, Christopher Morrow wrote: anyway... nit-picking-aside, cool that there's a way to figure this sort of thing out :) google has a similar method, which I can't find today :( dig -t txt o-o.myaddr.l.google.com

Re: whoami.akamai.net [was: Google Public DNS Problems?]

On 2 May 2013 15:41, Cameron Daniel wrote: > On 2013-05-03 4:57 am, Christopher Morrow wrote: >> >> anyway... nit-picking-aside, cool that there's a way to figure this sort >> of >> thing out :) >> google has a similar method, which I can't find today :( > webcrawler!!!> > > > dig -t txt o-o.myadd

Re: whoami.akamai.net [was: Google Public DNS Problems?]

On Thu, 02 May 2013 15:48:08 -0700, "Constantine A. Murenin" said: > On 2 May 2013 15:41, Cameron Daniel wrote: > > dig -t txt o-o.myaddr.l.google.com > > That's cool, but still no IPv6. > o-o.myaddr.l.google.com. 60 IN TXT "216.66.80.30" You're complaining that there's no IPv6 dat