Mailing List Archive

Google DNS
From my Digital Ocean VPS and office in midtown NY:

$ nslookup google.com 8.8.8.8
;; connection timed out; no servers could be reached
Re: Google DNS [ In reply to ]
Yes MTR to 8.8.8.8 is failing for us in the Northeast (NH).

On 08/15/2013 02:16 PM, Nick Lopez wrote:
> From my Digital Ocean VPS and office in midtown NY:
>
> $ nslookup google.com <http://google.com> 8.8.8.8
> ;; connection timed out; no servers could be reached
>
Re: Google DNS [ In reply to ]
On 2013-08-15, Nick Lopez <nlopez@gmail.com> sent:
> From my Digital Ocean VPS and office in midtown NY:
>
> $ nslookup google.com 8.8.8.8
> ;; connection timed out; no servers could be reached

Seeing the same here via Comcast in NH to both 8.8.8.8 and 8.8.4.4:

traceroute to 8.8.8.8 (8.8.8.8), 64 hops max, 52 byte packets
3 [AS7922] 24.104.68.169 (24.104.68.169) 4.580 ms 4.418 ms 4.436 ms
4 [AS7922] te-0-2-0-4-cr01.newyork.ny.ibone.comcast.net (68.86.84.49) 15.884 ms 11.907 ms 11.651 ms
5 [AS7922] he-0-11-0-0-pe03.111eighthave.ny.ibone.comcast.net (68.86.83.98) 11.416 ms 11.311 ms 11.457 ms
6 [AS7922] 23-30-206-126-static.hfc.comcastbusiness.net (23.30.206.126) 11.024 ms 12.916 ms 11.229 ms
7 [AS15169] 209.85.248.178 (209.85.248.178) 11.240 ms
[AS15169] 209.85.248.180 (209.85.248.180) 14.042 ms
[AS15169] 209.85.248.178 (209.85.248.178) 16.312 ms
8 [AS15169] 209.85.252.250 (209.85.252.250) 11.426 ms
[AS15169] 209.85.252.242 (209.85.252.242) 11.509 ms
[AS15169] 209.85.252.250 (209.85.252.250) 11.320 ms
9 [AS15169] 209.85.249.11 (209.85.249.11) 16.785 ms
[AS15169] 72.14.239.93 (72.14.239.93) 17.445 ms 17.388 ms
10 [AS15169] 72.14.235.10 (72.14.235.10) 24.389 ms
[AS15169] 72.14.235.12 (72.14.235.12) 24.569 ms
[AS15169] 66.249.95.231 (66.249.95.231) 24.536 ms
11 [AS15169] 72.14.234.65 (72.14.234.65) 24.117 ms 24.034 ms
[AS15169] 72.14.234.55 (72.14.234.55) 24.037 ms
12 * * *
13 * * *

--
Chip Marshall <chip@2bithacker.net>
http://2bithacker.net/
Re: Google DNS [ In reply to ]
Works for us – it may be GGC specific.



Frank



From: Outages [mailto:outages-bounces@outages.org] On Behalf Of Nick Lopez
Sent: Thursday, August 15, 2013 1:17 PM
To: outages@outages.org
Subject: [outages] Google DNS



From my Digital Ocean VPS and office in midtown NY:



$ nslookup google.com <http://google.com> 8.8.8.8

;; connection timed out; no servers could be reached
Re: Google DNS [ In reply to ]
Working fine from the West coast via both Comcast and HE.

Scott



On Thu, Aug 15, 2013 at 2:23 PM, Bret Clark <bclark@spectraaccess.com>wrote:

> Yes MTR to 8.8.8.8 is failing for us in the Northeast (NH).
>
> On 08/15/2013 02:16 PM, Nick Lopez wrote:
>
> From my Digital Ocean VPS and office in midtown NY:
>
> $ nslookup google.com 8.8.8.8
> ;; connection timed out; no servers could be reached
>
>
>
> _______________________________________________
> Outages mailing list
> Outages@outages.org
> https://puck.nether.net/mailman/listinfo/outages
>
>
Re: Google DNS [ In reply to ]
Fine from my office in Birmingham, AL and my VPS in Baltimore.
On 08/15/2013 01:16 PM, Nick Lopez wrote:
> From my Digital Ocean VPS and office in midtown NY:
>
> $ nslookup google.com <http://google.com> 8.8.8.8
> ;; connection timed out; no servers could be reached
>
>
>
> _______________________________________________
> Outages mailing list
> Outages@outages.org
> https://puck.nether.net/mailman/listinfo/outages
Re: Google DNS [ In reply to ]
Both visible in Toronto via TorIX:

BlackBox:~ jlixfeld$ mtr -c 1 -r 8.8.8.8
HOST: BlackBox.local Loss% Drop Rcv Snt Last Best Avg
1.|-- 192.168.66.1 0.0% 0 1 1 0.7 0.7 0.7
2.|-- vl4091.systems02.77mowat0 0.0% 0 1 1 1.0 1.0 1.0
3.|-- te0-0-0-2.bfr01.77mowatav 0.0% 0 1 1 1.3 1.3 1.3
4.|-- te0-0-0-1.bfr01.151fronts 0.0% 0 1 1 1.3 1.3 1.3
5.|-- gw-google.torontointernet 0.0% 0 1 1 1.0 1.0 1.0
6.|-- 216.239.47.114 0.0% 0 1 1 1.2 1.2 1.2
7.|-- 216.239.46.160 0.0% 0 1 1 16.9 16.9 16.9
8.|-- 209.85.241.22 0.0% 0 1 1 27.3 27.3 27.3
9.|-- 216.239.43.217 0.0% 0 1 1 29.1 29.1 29.1
10.|-- ??? 100.0 1 0 1 0.0 0.0 0.0
11.|-- google-public-dns-a.googl 0.0% 0 1 1 29.0 29.0 29.0


BlackBox:~ jlixfeld$ mtr -c 1 -r 8.8.4.4
HOST: BlackBox.local Loss% Drop Rcv Snt Last Best Avg
1.|-- 192.168.66.1 0.0% 0 1 1 0.9 0.9 0.9
2.|-- vl4091.systems02.77mowat0 0.0% 0 1 1 1.2 1.2 1.2
3.|-- te0-0-0-2.bfr01.77mowatav 0.0% 0 1 1 1.3 1.3 1.3
4.|-- te0-0-0-1.bfr01.151fronts 0.0% 0 1 1 1.6 1.6 1.6
5.|-- gw-google.torontointernet 0.0% 0 1 1 1.2 1.2 1.2
6.|-- 209.85.255.232 0.0% 0 1 1 1.0 1.0 1.0
7.|-- 216.239.46.162 0.0% 0 1 1 16.7 16.7 16.7
8.|-- 72.14.238.104 0.0% 0 1 1 29.2 29.2 29.2
9.|-- 216.239.46.193 0.0% 0 1 1 26.9 26.9 26.9
10.|-- ??? 100.0 1 0 1 0.0 0.0 0.0
11.|-- google-public-dns-b.googl 0.0% 0 1 1 26.9 26.9 26.9
BlackBox:~ jlixfeld$

On 2013-08-15, at 2:24 PM, Chip Marshall <chip@2bithacker.net> wrote:

> On 2013-08-15, Nick Lopez <nlopez@gmail.com> sent:
>> From my Digital Ocean VPS and office in midtown NY:
>>
>> $ nslookup google.com 8.8.8.8
>> ;; connection timed out; no servers could be reached
>
> Seeing the same here via Comcast in NH to both 8.8.8.8 and 8.8.4.4:
>
> traceroute to 8.8.8.8 (8.8.8.8), 64 hops max, 52 byte packets
> 3 [AS7922] 24.104.68.169 (24.104.68.169) 4.580 ms 4.418 ms 4.436 ms
> 4 [AS7922] te-0-2-0-4-cr01.newyork.ny.ibone.comcast.net (68.86.84.49) 15.884 ms 11.907 ms 11.651 ms
> 5 [AS7922] he-0-11-0-0-pe03.111eighthave.ny.ibone.comcast.net (68.86.83.98) 11.416 ms 11.311 ms 11.457 ms
> 6 [AS7922] 23-30-206-126-static.hfc.comcastbusiness.net (23.30.206.126) 11.024 ms 12.916 ms 11.229 ms
> 7 [AS15169] 209.85.248.178 (209.85.248.178) 11.240 ms
> [AS15169] 209.85.248.180 (209.85.248.180) 14.042 ms
> [AS15169] 209.85.248.178 (209.85.248.178) 16.312 ms
> 8 [AS15169] 209.85.252.250 (209.85.252.250) 11.426 ms
> [AS15169] 209.85.252.242 (209.85.252.242) 11.509 ms
> [AS15169] 209.85.252.250 (209.85.252.250) 11.320 ms
> 9 [AS15169] 209.85.249.11 (209.85.249.11) 16.785 ms
> [AS15169] 72.14.239.93 (72.14.239.93) 17.445 ms 17.388 ms
> 10 [AS15169] 72.14.235.10 (72.14.235.10) 24.389 ms
> [AS15169] 72.14.235.12 (72.14.235.12) 24.569 ms
> [AS15169] 66.249.95.231 (66.249.95.231) 24.536 ms
> 11 [AS15169] 72.14.234.65 (72.14.234.65) 24.117 ms 24.034 ms
> [AS15169] 72.14.234.55 (72.14.234.55) 24.037 ms
> 12 * * *
> 13 * * *
>
> --
> Chip Marshall <chip@2bithacker.net>
> http://2bithacker.net/
> _______________________________________________
> Outages mailing list
> Outages@outages.org
> https://puck.nether.net/mailman/listinfo/outages


_______________________________________________
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages
Re: Google DNS [ In reply to ]
Fine here in berkeley, california

.....................................
*Luke Rockwell*
Systems and Support Analyst
Information Technology

.....................................

Cal Alumni Association | UC Berkeley
1 Alumni House, Berkeley, CA 94720
*T* 510.900.8196
*F* 510.642.6252

.....................................

*140 Years of Alumni Excellence*
*Commitment, Support, Passion*

_____________________________________
*alumni.berkeley.edu*

_____________________________________
*Facebook <https://www.facebook.com/CalAlumni> |
LinkedIn<http://www.linkedin.com/groups?gid=70245>
*


On Thu, Aug 15, 2013 at 11:28 AM, John Barbieri <tenpin784@gmail.com> wrote:

> Fine from my office in Birmingham, AL and my VPS in Baltimore.
>
> On 08/15/2013 01:16 PM, Nick Lopez wrote:
>
> From my Digital Ocean VPS and office in midtown NY:
>
> $ nslookup google.com 8.8.8.8
> ;; connection timed out; no servers could be reached
>
>
>
> _______________________________________________
> Outages mailing listOutages@outages.orghttps://puck.nether.net/mailman/listinfo/outages
>
>
>
> _______________________________________________
> Outages mailing list
> Outages@outages.org
> https://puck.nether.net/mailman/listinfo/outages
>
>
Re: Google DNS [ In reply to ]
I'm on a Charter residential line mid-Wisconsin right now and I'm not
having any difficulty:

~$ traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
1 gatekeeper.anthonyrhook.com (192.168.1.1) 0.130 ms 0.189 ms 0.249 ms
2 10.138.192.1 (10.138.192.1) 5.099 ms 9.709 ms 10.642 ms
3 csw01wauswi-gbe-7-26.waus.wi.charter.com (96.34.16.198) 10.885 ms
10.885 ms 10.877 ms
4 crr01stptwi-tge-0-5-0-1.stpt.wi.charter.com (96.34.24.133) 15.480 ms
15.478 ms crr01stptwi-tge-0-5-0-3.stpt.wi.charter.com (96.34.24.224)
14.448 ms
5 crr02euclwi-tge-0-4-0-1.eucl.wi.charter.com (96.34.17.224) 23.917 ms
24.078 ms 22.857 ms
6 bbr02euclwi-tge-0-1-0-3.eucl.wi.charter.com (96.34.1.246) 21.031 ms
17.909 ms 18.810 ms
7 bbr01chcgil-bue-1.chcg.il.charter.com (96.34.0.9) 31.531 ms 24.120 ms
21.969 ms
8 prr01chcgil-bue-2.chcg.il.charter.com (96.34.3.9) 23.552 ms 24.304 ms
25.542 ms
9 96-34-152-30.static.unas.mo.charter.com (96.34.152.30) 23.117 ms
23.123 ms 22.917 ms
10 209.85.254.120 (209.85.254.120) 23.231 ms 23.261 ms 209.85.254.128
(209.85.254.128) 23.166 ms
11 72.14.237.130 (72.14.237.130) 23.152 ms 72.14.237.108 (72.14.237.108)
23.451 ms 72.14.237.110 (72.14.237.110) 23.434 ms
12 209.85.241.22 (209.85.241.22) 33.422 ms 34.325 ms 31.144 ms
13 216.239.46.191 (216.239.46.191) 33.523 ms 216.239.43.219
(216.239.43.219) 31.478 ms 216.239.46.191 (216.239.46.191) 33.477 ms
14 * * *
15 google-public-dns-a.google.com (8.8.8.8) 36.435 ms 36.632 ms 36.058
ms

$ nslookup google.com 8.8.8.8
Server: 8.8.8.8
Address: 8.8.8.8#53

Non-authoritative answer:
Name: google.com
Address: 173.194.46.70
Name: google.com
Address: 173.194.46.72
Name: google.com
Address: 173.194.46.78
Name: google.com
Address: 173.194.46.67
Name: google.com
Address: 173.194.46.68
Name: google.com
Address: 173.194.46.65
Name: google.com
Address: 173.194.46.71
Name: google.com
Address: 173.194.46.66
Name: google.com
Address: 173.194.46.64
Name: google.com
Address: 173.194.46.73
Name: google.com
Address: 173.194.46.69

$ nslookup google.com 8.8.4.4
Server: 8.8.4.4
Address: 8.8.4.4#53

Non-authoritative answer:
Name: google.com
Address: 173.194.46.70
Name: google.com
Address: 173.194.46.72
Name: google.com
Address: 173.194.46.78
Name: google.com
Address: 173.194.46.67
Name: google.com
Address: 173.194.46.68
Name: google.com
Address: 173.194.46.65
Name: google.com
Address: 173.194.46.71
Name: google.com
Address: 173.194.46.66
Name: google.com
Address: 173.194.46.64
Name: google.com
Address: 173.194.46.73
Name: google.com
Address: 173.194.46.69




On Thu, Aug 15, 2013 at 1:23 PM, Bret Clark <bclark@spectraaccess.com>wrote:

> Yes MTR to 8.8.8.8 is failing for us in the Northeast (NH).
>
>
> On 08/15/2013 02:16 PM, Nick Lopez wrote:
>
> From my Digital Ocean VPS and office in midtown NY:
>
> $ nslookup google.com 8.8.8.8
> ;; connection timed out; no servers could be reached
>
>
>
> _______________________________________________
> Outages mailing list
> Outages@outages.org
> https://puck.nether.net/mailman/listinfo/outages
>
>


--
- Anthony Hook
Re: Google DNS [ In reply to ]
Southwest via Charter is working

From: Outages [mailto:outages-bounces@outages.org] On Behalf Of Bret Clark
Sent: Thursday, August 15, 2013 2:24 PM
To: outages@outages.org
Subject: Re: [outages] Google DNS

Yes MTR to 8.8.8.8 is failing for us in the Northeast (NH).

On 08/15/2013 02:16 PM, Nick Lopez wrote:
From my Digital Ocean VPS and office in midtown NY:

$ nslookup google.com<http://google.com> 8.8.8.8
;; connection timed out; no servers could be reached
Re: Google DNS [ In reply to ]
It was borked for us on Comcast and Time Warner here in Atlanta from about
14:15 to 14:35 EDT.

------------------
Aubrey Wells
Director | Network Services
VocalCloud
888.305.3850
support@vocalcloud.com
www.vocalcloud.com


On Thu, Aug 15, 2013 at 2:49 PM, Anthony Hook <anthony.hook3@gmail.com>wrote:

> I'm on a Charter residential line mid-Wisconsin right now and I'm not
> having any difficulty:
>
> ~$ traceroute 8.8.8.8
> traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
> 1 gatekeeper.anthonyrhook.com (192.168.1.1) 0.130 ms 0.189 ms 0.249
> ms
> 2 10.138.192.1 (10.138.192.1) 5.099 ms 9.709 ms 10.642 ms
> 3 csw01wauswi-gbe-7-26.waus.wi.charter.com (96.34.16.198) 10.885 ms
> 10.885 ms 10.877 ms
> 4 crr01stptwi-tge-0-5-0-1.stpt.wi.charter.com (96.34.24.133) 15.480 ms
> 15.478 ms crr01stptwi-tge-0-5-0-3.stpt.wi.charter.com (96.34.24.224)
> 14.448 ms
> 5 crr02euclwi-tge-0-4-0-1.eucl.wi.charter.com (96.34.17.224) 23.917 ms
> 24.078 ms 22.857 ms
> 6 bbr02euclwi-tge-0-1-0-3.eucl.wi.charter.com (96.34.1.246) 21.031 ms
> 17.909 ms 18.810 ms
> 7 bbr01chcgil-bue-1.chcg.il.charter.com (96.34.0.9) 31.531 ms 24.120
> ms 21.969 ms
> 8 prr01chcgil-bue-2.chcg.il.charter.com (96.34.3.9) 23.552 ms 24.304
> ms 25.542 ms
> 9 96-34-152-30.static.unas.mo.charter.com (96.34.152.30) 23.117 ms
> 23.123 ms 22.917 ms
> 10 209.85.254.120 (209.85.254.120) 23.231 ms 23.261 ms 209.85.254.128
> (209.85.254.128) 23.166 ms
> 11 72.14.237.130 (72.14.237.130) 23.152 ms 72.14.237.108 (72.14.237.108)
> 23.451 ms 72.14.237.110 (72.14.237.110) 23.434 ms
> 12 209.85.241.22 (209.85.241.22) 33.422 ms 34.325 ms 31.144 ms
> 13 216.239.46.191 (216.239.46.191) 33.523 ms 216.239.43.219
> (216.239.43.219) 31.478 ms 216.239.46.191 (216.239.46.191) 33.477 ms
> 14 * * *
> 15 google-public-dns-a.google.com (8.8.8.8) 36.435 ms 36.632 ms
> 36.058 ms
>
> $ nslookup google.com 8.8.8.8
> Server: 8.8.8.8
> Address: 8.8.8.8#53
>
> Non-authoritative answer:
> Name: google.com
> Address: 173.194.46.70
> Name: google.com
> Address: 173.194.46.72
> Name: google.com
> Address: 173.194.46.78
> Name: google.com
> Address: 173.194.46.67
> Name: google.com
> Address: 173.194.46.68
> Name: google.com
> Address: 173.194.46.65
> Name: google.com
> Address: 173.194.46.71
> Name: google.com
> Address: 173.194.46.66
> Name: google.com
> Address: 173.194.46.64
> Name: google.com
> Address: 173.194.46.73
> Name: google.com
> Address: 173.194.46.69
>
> $ nslookup google.com 8.8.4.4
> Server: 8.8.4.4
> Address: 8.8.4.4#53
>
> Non-authoritative answer:
> Name: google.com
> Address: 173.194.46.70
> Name: google.com
> Address: 173.194.46.72
> Name: google.com
> Address: 173.194.46.78
> Name: google.com
> Address: 173.194.46.67
> Name: google.com
> Address: 173.194.46.68
> Name: google.com
> Address: 173.194.46.65
> Name: google.com
> Address: 173.194.46.71
> Name: google.com
> Address: 173.194.46.66
> Name: google.com
> Address: 173.194.46.64
> Name: google.com
> Address: 173.194.46.73
> Name: google.com
> Address: 173.194.46.69
>
>
>
>
> On Thu, Aug 15, 2013 at 1:23 PM, Bret Clark <bclark@spectraaccess.com>wrote:
>
>> Yes MTR to 8.8.8.8 is failing for us in the Northeast (NH).
>>
>>
>> On 08/15/2013 02:16 PM, Nick Lopez wrote:
>>
>> From my Digital Ocean VPS and office in midtown NY:
>>
>> $ nslookup google.com 8.8.8.8
>> ;; connection timed out; no servers could be reached
>>
>>
>>
>> _______________________________________________
>> Outages mailing list
>> Outages@outages.org
>> https://puck.nether.net/mailman/listinfo/outages
>>
>>
>
>
> --
> - Anthony Hook
>
> _______________________________________________
> Outages mailing list
> Outages@outages.org
> https://puck.nether.net/mailman/listinfo/outages
>
>
Re: Google DNS [ In reply to ]
Hi, we (Google Public DNS) just experienced a short period of outage in
certain east coast area. The service has been recovered.

Thanks,
Yunhong


On Thu, Aug 15, 2013 at 2:53 PM, Stephens, Jamie A <
Jamie.Stephens@charter.com> wrote:

> Southwest via Charter is working****
>
> ** **
>
> *From:* Outages [mailto:outages-bounces@outages.org] *On Behalf Of *Bret
> Clark
> *Sent:* Thursday, August 15, 2013 2:24 PM
> *To:* outages@outages.org
> *Subject:* Re: [outages] Google DNS****
>
> ** **
>
> Yes MTR to 8.8.8.8 is failing for us in the Northeast (NH).
>
> On 08/15/2013 02:16 PM, Nick Lopez wrote:****
>
> From my Digital Ocean VPS and office in midtown NY: ****
>
> ** **
>
> $ nslookup google.com 8.8.8.8****
>
> ;; connection timed out; no servers could be reached****
>
> ** **
>
> ** **
>
> _______________________________________________
> Outages mailing list
> Outages@outages.org
> https://puck.nether.net/mailman/listinfo/outages
>
>
Re: Google DNS [ In reply to ]
My monitoring system is getting responses. Just asking it a simple A
record.

Josh Luthman
Office: 937-552-2340
Direct: 937-552-2343
1100 Wayne St
Suite 1337
Troy, OH 45373
On Dec 6, 2013 1:31 PM, "Luke Rockwell" <luke.rockwell@alumni.berkeley.edu>
wrote:

> Anybody else having issues with google dns?
>
> .....................................
> *Luke Rockwell*
> Systems and Support Analyst
> Information Technology
>
>
>
> _______________________________________________
> Outages mailing list
> Outages@outages.org
> https://puck.nether.net/mailman/listinfo/outages
>
>
Re: Google DNS [ In reply to ]
On 12/06/13 10:25 -0800, Luke Rockwell wrote:
>Anybody else having issues with google dns?

No problems here (south central US):

$ time dig +short @8.8.8.8 google.com a
74.125.225.226
74.125.225.230
74.125.225.233
74.125.225.238
74.125.225.232
74.125.225.227
74.125.225.225
74.125.225.229
74.125.225.224
74.125.225.231
74.125.225.228

real 0m0.077s
user 0m0.012s
sys 0m0.000s

$ time dig +short @8.8.4.4 google.com a
74.125.225.231
74.125.225.229
74.125.225.227
74.125.225.238
74.125.225.224
74.125.225.233
74.125.225.230
74.125.225.226
74.125.225.225
74.125.225.228
74.125.225.232

real 0m0.056s
user 0m0.012s
sys 0m0.000s

$ traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
4 olp-67-217-150-202.olp.net (67.217.150.202) 1.758 ms 1.756 ms 1.709
ms
5 vlan3823.car1.Dallas1.Level3.net (4.59.113.73) 33.776 ms 33.781 ms
33.773 ms
6 * * *
7 Google-level3-3x10G.Dallas.Level3.net (4.68.70.166) 33.395 ms 36.129
ms 36.112 ms
8 * * *
9 72.14.237.215 (72.14.237.215) 33.802 ms 72.14.237.221 (72.14.237.221)
47.775 ms 72.14.237.215 (72.14.237.215) 34.017 ms
10 209.85.243.178 (209.85.243.178) 41.019 ms 216.239.47.121
(216.239.47.121) 41.025 ms 41.115 ms
11 216.239.46.59 (216.239.46.59) 41.332 ms 216.239.46.39 (216.239.46.39)
41.934 ms 216.239.46.59 (216.239.46.59) 41.939 ms
12 * * *
13 google-public-dns-a.google.com (8.8.8.8) 40.401 ms 40.394 ms 40.115
ms


$ traceroute 8.8.4.4
traceroute to 8.8.4.4 (8.8.4.4), 30 hops max, 60 byte packets
4 olp-67-217-150-202.olp.net (67.217.150.202) 2.095 ms 2.089 ms 2.083
ms
5 vlan3823.car1.dallas1.level3.net (4.59.113.73) 33.971 ms 33.972 ms
33.966 ms
6 * * *
7 google-level3-3x10g.dallas.level3.net (4.68.70.166) 33.683 ms 33.691
ms 33.680 ms
8 72.14.233.67 (72.14.233.67) 33.840 ms 33.841 ms 72.14.233.65
(72.14.233.65) 33.963 ms
9 72.14.237.221 (72.14.237.221) 35.000 ms 72.14.237.217 (72.14.237.217)
35.000 ms 72.14.237.219 (72.14.237.219) 35.104 ms
10 209.85.243.178 (209.85.243.178) 41.348 ms 41.352 ms 41.491 ms
11 216.239.46.63 (216.239.46.63) 41.612 ms 41.612 ms 216.239.46.61
(216.239.46.61) 41.110 ms
12 * * *
13 google-public-dns-b.google.com (8.8.4.4) 41.055 ms 40.932 ms 40.722
ms



--
Dan White
_______________________________________________
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages
Re: Google DNS [ In reply to ]
It is now responding. My routers show it was offline for 5 minutes

.....................................
*Luke Rockwell*
Systems and Support Analyst
Information Technology

.....................................

Cal Alumni Association | UC Berkeley
1 Alumni House, Berkeley, CA 94720
*T* 510.900.8196
*F* 510.642.6252

.....................................

*140 Years of Alumni Excellence*
*Commitment, Support, Passion*

_____________________________________
*alumni.berkeley.edu <http://alumni.berkeley.edu/>*

_____________________________________
*Facebook <https://www.facebook.com/CalAlumni> | LinkedIn
<http://www.linkedin.com/groups?gid=70245>*


On Fri, Dec 6, 2013 at 10:41 AM, Dan White <dwhite@olp.net> wrote:

> On 12/06/13 10:25 -0800, Luke Rockwell wrote:
>
>> Anybody else having issues with google dns?
>>
>
> No problems here (south central US):
>
> $ time dig +short @8.8.8.8 google.com a
> 74.125.225.226
> 74.125.225.230
> 74.125.225.233
> 74.125.225.238
> 74.125.225.232
> 74.125.225.227
> 74.125.225.225
> 74.125.225.229
> 74.125.225.224
> 74.125.225.231
> 74.125.225.228
>
> real 0m0.077s
> user 0m0.012s
> sys 0m0.000s
>
> $ time dig +short @8.8.4.4 google.com a
> 74.125.225.231
> 74.125.225.229
> 74.125.225.227
> 74.125.225.238
> 74.125.225.224
> 74.125.225.233
> 74.125.225.230
> 74.125.225.226
> 74.125.225.225
> 74.125.225.228
> 74.125.225.232
>
> real 0m0.056s
> user 0m0.012s
> sys 0m0.000s
>
> $ traceroute 8.8.8.8
> traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
> 4 olp-67-217-150-202.olp.net (67.217.150.202) 1.758 ms 1.756 ms 1.709
> ms
> 5 vlan3823.car1.Dallas1.Level3.net (4.59.113.73) 33.776 ms 33.781 ms
> 33.773 ms
> 6 * * *
> 7 Google-level3-3x10G.Dallas.Level3.net (4.68.70.166) 33.395 ms 36.129
> ms 36.112 ms
> 8 * * *
> 9 72.14.237.215 (72.14.237.215) 33.802 ms 72.14.237.221 (72.14.237.221)
> 47.775 ms 72.14.237.215 (72.14.237.215) 34.017 ms
> 10 209.85.243.178 (209.85.243.178) 41.019 ms 216.239.47.121
> (216.239.47.121) 41.025 ms 41.115 ms
> 11 216.239.46.59 (216.239.46.59) 41.332 ms 216.239.46.39 (216.239.46.39)
> 41.934 ms 216.239.46.59 (216.239.46.59) 41.939 ms
> 12 * * *
> 13 google-public-dns-a.google.com (8.8.8.8) 40.401 ms 40.394 ms 40.115
> ms
>
>
> $ traceroute 8.8.4.4
> traceroute to 8.8.4.4 (8.8.4.4), 30 hops max, 60 byte packets
> 4 olp-67-217-150-202.olp.net (67.217.150.202) 2.095 ms 2.089 ms 2.083
> ms
> 5 vlan3823.car1.dallas1.level3.net (4.59.113.73) 33.971 ms 33.972 ms
> 33.966 ms
> 6 * * *
> 7 google-level3-3x10g.dallas.level3.net (4.68.70.166) 33.683 ms 33.691
> ms 33.680 ms
> 8 72.14.233.67 (72.14.233.67) 33.840 ms 33.841 ms 72.14.233.65
> (72.14.233.65) 33.963 ms
> 9 72.14.237.221 (72.14.237.221) 35.000 ms 72.14.237.217 (72.14.237.217)
> 35.000 ms 72.14.237.219 (72.14.237.219) 35.104 ms
> 10 209.85.243.178 (209.85.243.178) 41.348 ms 41.352 ms 41.491 ms
> 11 216.239.46.63 (216.239.46.63) 41.612 ms 41.612 ms 216.239.46.61
> (216.239.46.61) 41.110 ms
> 12 * * *
> 13 google-public-dns-b.google.com (8.8.4.4) 41.055 ms 40.932 ms 40.722
> ms
>
>
>
> --
> Dan White
>
Re: Google DNS [ In reply to ]
In the future, a source IP, destination IP (Google has more than one DNS
server), and traceroute would be useful.

Damian


On Fri, Dec 6, 2013 at 10:25 AM, Luke Rockwell <
luke.rockwell@alumni.berkeley.edu> wrote:

> Anybody else having issues with google dns?
>
> .....................................
> *Luke Rockwell*
> Systems and Support Analyst
> Information Technology
>
>
>
> _______________________________________________
> Outages mailing list
> Outages@outages.org
> https://puck.nether.net/mailman/listinfo/outages
>
>
Re: Google DNS [ In reply to ]
On 12/06/13 12:41 -0600, Dan White wrote:
>On 12/06/13 10:25 -0800, Luke Rockwell wrote:
>>Anybody else having issues with google dns?
>
>No problems here (south central US):
>
>$ time dig +short @8.8.8.8 google.com a
>74.125.225.226
>74.125.225.230
>74.125.225.233
>74.125.225.238
>74.125.225.232
>74.125.225.227
>74.125.225.225
>74.125.225.229
>74.125.225.224
>74.125.225.231
>74.125.225.228
>
>real 0m0.077s
>user 0m0.012s
>sys 0m0.000s

One of our DNS servers just had incorrect data cached for google.com and
www.google.com:

dwhite@quark:~$ dig www.google.com

;; QUESTION SECTION:
;www.google.com. IN A

;; ANSWER SECTION:
www.google.com. 24 IN A 201.130.208.23
www.google.com. 24 IN A 201.130.208.44
www.google.com. 24 IN A 201.130.208.34
www.google.com. 24 IN A 201.130.208.45
www.google.com. 24 IN A 201.130.208.29
www.google.com. 24 IN A 201.130.208.30
www.google.com. 24 IN A 201.130.208.53
www.google.com. 24 IN A 201.130.208.38
www.google.com. 24 IN A 201.130.208.19
www.google.com. 24 IN A 201.130.208.49
www.google.com. 24 IN A 201.130.208.59
www.google.com. 24 IN A 201.130.208.57
www.google.com. 24 IN A 201.130.208.27
www.google.com. 24 IN A 201.130.208.42
www.google.com. 24 IN A 201.130.208.15

After the 24 second cache timeout, the correct (google space) IPs
populated:

;; ANSWER SECTION:
google.com. 138 IN A 74.125.227.104
google.com. 138 IN A 74.125.227.100
google.com. 138 IN A 74.125.227.101
google.com. 138 IN A 74.125.227.102
google.com. 138 IN A 74.125.227.105
google.com. 138 IN A 74.125.227.97
google.com. 138 IN A 74.125.227.98
google.com. 138 IN A 74.125.227.110
google.com. 138 IN A 74.125.227.96
google.com. 138 IN A 74.125.227.103
google.com. 138 IN A 74.125.227.99

I did not notice this on any other DNS servers.

--
Dan White
_______________________________________________
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages
Re: Google DNS [ In reply to ]
Those are valid Google IPs, so this is likely working as intended and you
were just temporarily being load-balanced to a different datacenter. If
you're still concerned, please send me more detail off-list.

Damian


On Fri, Dec 6, 2013 at 1:27 PM, Dan White <dwhite@olp.net> wrote:

> On 12/06/13 12:41 -0600, Dan White wrote:
>
>> On 12/06/13 10:25 -0800, Luke Rockwell wrote:
>>
>>> Anybody else having issues with google dns?
>>>
>>
>> No problems here (south central US):
>>
>> $ time dig +short @8.8.8.8 google.com a
>> 74.125.225.226
>> 74.125.225.230
>> 74.125.225.233
>> 74.125.225.238
>> 74.125.225.232
>> 74.125.225.227
>> 74.125.225.225
>> 74.125.225.229
>> 74.125.225.224
>> 74.125.225.231
>> 74.125.225.228
>>
>> real 0m0.077s
>> user 0m0.012s
>> sys 0m0.000s
>>
>
> One of our DNS servers just had incorrect data cached for google.com and
> www.google.com:
>
> dwhite@quark:~$ dig www.google.com
>
> ;; QUESTION SECTION:
> ;www.google.com. IN A
>
> ;; ANSWER SECTION:
> www.google.com. 24 IN A 201.130.208.23
> www.google.com. 24 IN A 201.130.208.44
> www.google.com. 24 IN A 201.130.208.34
> www.google.com. 24 IN A 201.130.208.45
> www.google.com. 24 IN A 201.130.208.29
> www.google.com. 24 IN A 201.130.208.30
> www.google.com. 24 IN A 201.130.208.53
> www.google.com. 24 IN A 201.130.208.38
> www.google.com. 24 IN A 201.130.208.19
> www.google.com. 24 IN A 201.130.208.49
> www.google.com. 24 IN A 201.130.208.59
> www.google.com. 24 IN A 201.130.208.57
> www.google.com. 24 IN A 201.130.208.27
> www.google.com. 24 IN A 201.130.208.42
> www.google.com. 24 IN A 201.130.208.15
>
> After the 24 second cache timeout, the correct (google space) IPs
> populated:
>
> ;; ANSWER SECTION:
> google.com. 138 IN A 74.125.227.104
> google.com. 138 IN A 74.125.227.100
> google.com. 138 IN A 74.125.227.101
> google.com. 138 IN A 74.125.227.102
> google.com. 138 IN A 74.125.227.105
> google.com. 138 IN A 74.125.227.97
> google.com. 138 IN A 74.125.227.98
> google.com. 138 IN A 74.125.227.110
> google.com. 138 IN A 74.125.227.96
> google.com. 138 IN A 74.125.227.103
> google.com. 138 IN A 74.125.227.99
>
> I did not notice this on any other DNS servers.
>
>
> --
> Dan White
> _______________________________________________
> Outages mailing list
> Outages@outages.org
> https://puck.nether.net/mailman/listinfo/outages
>
Re: Google DNS [ In reply to ]
If they are valid Google IPs then your rDNS could do with some updating...


23.208.130.201.in-addr.arpa name =
201-130-208-23-cable.cybercable.net.mx.

inetnum: 201.130.192/18
status: allocated
aut-num: N/A
owner: Cablevision Red, S.A de C.V.
ownerid: MX-CRSC10-LACNIC
responsible: Luis Vielma Ordo<F1>es
address: Av. Naciones Unidas, 5526, Col. Vallarta Universidad
address: 45110 - Guadalajara - JL
country: MX


Scott




On Fri, Dec 6, 2013 at 2:14 PM, Damian Menscher <damian@google.com> wrote:

> Those are valid Google IPs, so this is likely working as intended and you
> were just temporarily being load-balanced to a different datacenter. If
> you're still concerned, please send me more detail off-list.
>
> Damian
>
>
> On Fri, Dec 6, 2013 at 1:27 PM, Dan White <dwhite@olp.net> wrote:
>
>> On 12/06/13 12:41 -0600, Dan White wrote:
>>
>>> On 12/06/13 10:25 -0800, Luke Rockwell wrote:
>>>
>>>> Anybody else having issues with google dns?
>>>>
>>>
>>> No problems here (south central US):
>>>
>>> $ time dig +short @8.8.8.8 google.com a
>>> 74.125.225.226
>>> 74.125.225.230
>>> 74.125.225.233
>>> 74.125.225.238
>>> 74.125.225.232
>>> 74.125.225.227
>>> 74.125.225.225
>>> 74.125.225.229
>>> 74.125.225.224
>>> 74.125.225.231
>>> 74.125.225.228
>>>
>>> real 0m0.077s
>>> user 0m0.012s
>>> sys 0m0.000s
>>>
>>
>> One of our DNS servers just had incorrect data cached for google.com and
>> www.google.com:
>>
>> dwhite@quark:~$ dig www.google.com
>>
>> ;; QUESTION SECTION:
>> ;www.google.com. IN A
>>
>> ;; ANSWER SECTION:
>> www.google.com. 24 IN A 201.130.208.23
>> www.google.com. 24 IN A 201.130.208.44
>> www.google.com. 24 IN A 201.130.208.34
>> www.google.com. 24 IN A 201.130.208.45
>> www.google.com. 24 IN A 201.130.208.29
>> www.google.com. 24 IN A 201.130.208.30
>> www.google.com. 24 IN A 201.130.208.53
>> www.google.com. 24 IN A 201.130.208.38
>> www.google.com. 24 IN A 201.130.208.19
>> www.google.com. 24 IN A 201.130.208.49
>> www.google.com. 24 IN A 201.130.208.59
>> www.google.com. 24 IN A 201.130.208.57
>> www.google.com. 24 IN A 201.130.208.27
>> www.google.com. 24 IN A 201.130.208.42
>> www.google.com. 24 IN A 201.130.208.15
>>
>> After the 24 second cache timeout, the correct (google space) IPs
>> populated:
>>
>> ;; ANSWER SECTION:
>> google.com. 138 IN A 74.125.227.104
>> google.com. 138 IN A 74.125.227.100
>> google.com. 138 IN A 74.125.227.101
>> google.com. 138 IN A 74.125.227.102
>> google.com. 138 IN A 74.125.227.105
>> google.com. 138 IN A 74.125.227.97
>> google.com. 138 IN A 74.125.227.98
>> google.com. 138 IN A 74.125.227.110
>> google.com. 138 IN A 74.125.227.96
>> google.com. 138 IN A 74.125.227.103
>> google.com. 138 IN A 74.125.227.99
>>
>> I did not notice this on any other DNS servers.
>>
>>
>> --
>> Dan White
>> _______________________________________________
>> Outages mailing list
>> Outages@outages.org
>> https://puck.nether.net/mailman/listinfo/outages
>>
>
>
> _______________________________________________
> Outages mailing list
> Outages@outages.org
> https://puck.nether.net/mailman/listinfo/outages
>
>
Re: Google DNS [ In reply to ]
I should have noted that during the time that www.google.com was resolving
to 201.130.208.x, access to google.com and youtube.com was unavailable
(timeouts within a browser).

On 12/06/13 14:14 -0800, Damian Menscher wrote:
>Those are valid Google IPs, so this is likely working as intended and you
>were just temporarily being load-balanced to a different datacenter. If
>you're still concerned, please send me more detail off-list.
>
>Damian
>
>
>On Fri, Dec 6, 2013 at 1:27 PM, Dan White <dwhite@olp.net> wrote:
>
>> On 12/06/13 12:41 -0600, Dan White wrote:
>>
>>> On 12/06/13 10:25 -0800, Luke Rockwell wrote:
>>>
>>>> Anybody else having issues with google dns?
>>>>
>>>
>>> No problems here (south central US):
>>>
>>> $ time dig +short @8.8.8.8 google.com a
>>> 74.125.225.226
>>> 74.125.225.230
>>> 74.125.225.233
>>> 74.125.225.238
>>> 74.125.225.232
>>> 74.125.225.227
>>> 74.125.225.225
>>> 74.125.225.229
>>> 74.125.225.224
>>> 74.125.225.231
>>> 74.125.225.228
>>>
>>> real 0m0.077s
>>> user 0m0.012s
>>> sys 0m0.000s
>>>
>>
>> One of our DNS servers just had incorrect data cached for google.com and
>> www.google.com:
>>
>> dwhite@quark:~$ dig www.google.com
>>
>> ;; QUESTION SECTION:
>> ;www.google.com. IN A
>>
>> ;; ANSWER SECTION:
>> www.google.com. 24 IN A 201.130.208.23
>> www.google.com. 24 IN A 201.130.208.44
>> www.google.com. 24 IN A 201.130.208.34
>> www.google.com. 24 IN A 201.130.208.45
>> www.google.com. 24 IN A 201.130.208.29
>> www.google.com. 24 IN A 201.130.208.30
>> www.google.com. 24 IN A 201.130.208.53
>> www.google.com. 24 IN A 201.130.208.38
>> www.google.com. 24 IN A 201.130.208.19
>> www.google.com. 24 IN A 201.130.208.49
>> www.google.com. 24 IN A 201.130.208.59
>> www.google.com. 24 IN A 201.130.208.57
>> www.google.com. 24 IN A 201.130.208.27
>> www.google.com. 24 IN A 201.130.208.42
>> www.google.com. 24 IN A 201.130.208.15
>>
>> After the 24 second cache timeout, the correct (google space) IPs
>> populated:
>>
>> ;; ANSWER SECTION:
>> google.com. 138 IN A 74.125.227.104
>> google.com. 138 IN A 74.125.227.100
>> google.com. 138 IN A 74.125.227.101
>> google.com. 138 IN A 74.125.227.102
>> google.com. 138 IN A 74.125.227.105
>> google.com. 138 IN A 74.125.227.97
>> google.com. 138 IN A 74.125.227.98
>> google.com. 138 IN A 74.125.227.110
>> google.com. 138 IN A 74.125.227.96
>> google.com. 138 IN A 74.125.227.103
>> google.com. 138 IN A 74.125.227.99
>>
>> I did not notice this on any other DNS servers.

--
Dan White
_______________________________________________
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages
Re: Google DNS [ In reply to ]
On Dec 6, 2013, at 5:17 PM, Scott Howard <scott@doc.net.au> wrote:

> If they are valid Google IPs then your rDNS could do with some updating…
>

Unfortunately not all valid Google IPs are actually, um, Google IPs. Some are Google Caches: https://peering.google.com/about/ggc.html

For various non-technical, contractual type reasons these are not all documented anywhere publicly…

W


> 23.208.130.201.in-addr.arpa name = 201-130-208-23-cable.cybercable.net.mx.
>
> inetnum: 201.130.192/18
> status: allocated
> aut-num: N/A
> owner: Cablevision Red, S.A de C.V.
> ownerid: MX-CRSC10-LACNIC
> responsible: Luis Vielma Ordo<F1>es
> address: Av. Naciones Unidas, 5526, Col. Vallarta Universidad
> address: 45110 - Guadalajara - JL
> country: MX
>
>
> Scott
>
>
>
>
> On Fri, Dec 6, 2013 at 2:14 PM, Damian Menscher <damian@google.com> wrote:
> Those are valid Google IPs, so this is likely working as intended and you were just temporarily being load-balanced to a different datacenter. If you're still concerned, please send me more detail off-list.
>
> Damian
>
>
> On Fri, Dec 6, 2013 at 1:27 PM, Dan White <dwhite@olp.net> wrote:
> On 12/06/13 12:41 -0600, Dan White wrote:
> On 12/06/13 10:25 -0800, Luke Rockwell wrote:
> Anybody else having issues with google dns?
>
> No problems here (south central US):
>
> $ time dig +short @8.8.8.8 google.com a
> 74.125.225.226
> 74.125.225.230
> 74.125.225.233
> 74.125.225.238
> 74.125.225.232
> 74.125.225.227
> 74.125.225.225
> 74.125.225.229
> 74.125.225.224
> 74.125.225.231
> 74.125.225.228
>
> real 0m0.077s
> user 0m0.012s
> sys 0m0.000s
>
> One of our DNS servers just had incorrect data cached for google.com and
> www.google.com:
>
> dwhite@quark:~$ dig www.google.com
>
> ;; QUESTION SECTION:
> ;www.google.com. IN A
>
> ;; ANSWER SECTION:
> www.google.com. 24 IN A 201.130.208.23
> www.google.com. 24 IN A 201.130.208.44
> www.google.com. 24 IN A 201.130.208.34
> www.google.com. 24 IN A 201.130.208.45
> www.google.com. 24 IN A 201.130.208.29
> www.google.com. 24 IN A 201.130.208.30
> www.google.com. 24 IN A 201.130.208.53
> www.google.com. 24 IN A 201.130.208.38
> www.google.com. 24 IN A 201.130.208.19
> www.google.com. 24 IN A 201.130.208.49
> www.google.com. 24 IN A 201.130.208.59
> www.google.com. 24 IN A 201.130.208.57
> www.google.com. 24 IN A 201.130.208.27
> www.google.com. 24 IN A 201.130.208.42
> www.google.com. 24 IN A 201.130.208.15
>
> After the 24 second cache timeout, the correct (google space) IPs
> populated:
>
> ;; ANSWER SECTION:
> google.com. 138 IN A 74.125.227.104
> google.com. 138 IN A 74.125.227.100
> google.com. 138 IN A 74.125.227.101
> google.com. 138 IN A 74.125.227.102
> google.com. 138 IN A 74.125.227.105
> google.com. 138 IN A 74.125.227.97
> google.com. 138 IN A 74.125.227.98
> google.com. 138 IN A 74.125.227.110
> google.com. 138 IN A 74.125.227.96
> google.com. 138 IN A 74.125.227.103
> google.com. 138 IN A 74.125.227.99
>
> I did not notice this on any other DNS servers.
>
>
> --
> Dan White
> _______________________________________________
> Outages mailing list
> Outages@outages.org
> https://puck.nether.net/mailman/listinfo/outages
>
>
> _______________________________________________
> Outages mailing list
> Outages@outages.org
> https://puck.nether.net/mailman/listinfo/outages
>
>
> _______________________________________________
> Outages mailing list
> Outages@outages.org
> https://puck.nether.net/mailman/listinfo/outages

--
"Let's just say that if complete and utter chaos was lightning, he'd be the sort to stand on a hilltop in a thunderstorm wearing wet copper armour and shouting 'All gods are bastards'."

-- Rincewind discussing Twoflower (Terry Pratchett, The Colour of Magic)



_______________________________________________
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages
Re: Google DNS [ In reply to ]
Thanks for the additional detail. The responsible team is investigating
what happened.

Damian


On Fri, Dec 6, 2013 at 2:25 PM, Dan White <dwhite@olp.net> wrote:

> I should have noted that during the time that www.google.com was resolving
> to 201.130.208.x, access to google.com and youtube.com was unavailable
> (timeouts within a browser).
>
>
> On 12/06/13 14:14 -0800, Damian Menscher wrote:
>
>> Those are valid Google IPs, so this is likely working as intended and you
>> were just temporarily being load-balanced to a different datacenter. If
>> you're still concerned, please send me more detail off-list.
>>
>> Damian
>>
>>
>> On Fri, Dec 6, 2013 at 1:27 PM, Dan White <dwhite@olp.net> wrote:
>>
>> On 12/06/13 12:41 -0600, Dan White wrote:
>>>
>>> On 12/06/13 10:25 -0800, Luke Rockwell wrote:
>>>>
>>>> Anybody else having issues with google dns?
>>>>>
>>>>>
>>>> No problems here (south central US):
>>>>
>>>> $ time dig +short @8.8.8.8 google.com a
>>>> 74.125.225.226
>>>> 74.125.225.230
>>>> 74.125.225.233
>>>> 74.125.225.238
>>>> 74.125.225.232
>>>> 74.125.225.227
>>>> 74.125.225.225
>>>> 74.125.225.229
>>>> 74.125.225.224
>>>> 74.125.225.231
>>>> 74.125.225.228
>>>>
>>>> real 0m0.077s
>>>> user 0m0.012s
>>>> sys 0m0.000s
>>>>
>>>>
>>> One of our DNS servers just had incorrect data cached for google.com and
>>> www.google.com:
>>>
>>> dwhite@quark:~$ dig www.google.com
>>>
>>> ;; QUESTION SECTION:
>>> ;www.google.com. IN A
>>>
>>> ;; ANSWER SECTION:
>>> www.google.com. 24 IN A 201.130.208.23
>>> www.google.com. 24 IN A 201.130.208.44
>>> www.google.com. 24 IN A 201.130.208.34
>>> www.google.com. 24 IN A 201.130.208.45
>>> www.google.com. 24 IN A 201.130.208.29
>>> www.google.com. 24 IN A 201.130.208.30
>>> www.google.com. 24 IN A 201.130.208.53
>>> www.google.com. 24 IN A 201.130.208.38
>>> www.google.com. 24 IN A 201.130.208.19
>>> www.google.com. 24 IN A 201.130.208.49
>>> www.google.com. 24 IN A 201.130.208.59
>>> www.google.com. 24 IN A 201.130.208.57
>>> www.google.com. 24 IN A 201.130.208.27
>>> www.google.com. 24 IN A 201.130.208.42
>>> www.google.com. 24 IN A 201.130.208.15
>>>
>>> After the 24 second cache timeout, the correct (google space) IPs
>>> populated:
>>>
>>> ;; ANSWER SECTION:
>>> google.com. 138 IN A 74.125.227.104
>>> google.com. 138 IN A 74.125.227.100
>>> google.com. 138 IN A 74.125.227.101
>>> google.com. 138 IN A 74.125.227.102
>>> google.com. 138 IN A 74.125.227.105
>>> google.com. 138 IN A 74.125.227.97
>>> google.com. 138 IN A 74.125.227.98
>>> google.com. 138 IN A 74.125.227.110
>>> google.com. 138 IN A 74.125.227.96
>>> google.com. 138 IN A 74.125.227.103
>>> google.com. 138 IN A 74.125.227.99
>>>
>>> I did not notice this on any other DNS servers.
>>>
>>
> --
> Dan White
>
Re: Google DNS [ In reply to ]
Ok out of New York, thus far.

On Thu, May 13, 2021 at 10:45 AM John Cornelius via Outages <
outages@outages.org> wrote:

> Getting reports of issues with Google DNS. Can anyone confirm similar
> issues?
> Location: Kentucky.
>
> _______________________________________________
> Outages mailing list
> Outages@outages.org
> https://puck.nether.net/mailman/listinfo/outages
>
Re: Google DNS [ In reply to ]
Working reliably here in Phoenix from both Phoenix NAP's blended
connections and Cox residential service.

On Thu, May 13, 2021 at 7:45 AM John Cornelius via Outages <
outages@outages.org> wrote:

> Getting reports of issues with Google DNS. Can anyone confirm similar
> issues?
> Location: Kentucky.
>
> _______________________________________________
> Outages mailing list
> Outages@outages.org
> https://puck.nether.net/mailman/listinfo/outages
>


--
Carlos Alvarez
602-368-6403
Re: Google DNS [ In reply to ]
Looking fine for me on Metronet FTTH, and a Clink business circuit here
in Lexington, KY:

;; Query time: 74 msec
> ;; SERVER: 8.8.8.8#53(8.8.8.8)
> ;; WHEN: Thu May 13 10:44:24 EDT 2021
> ;; MSG SIZE rcvd: 54
> --
> ;; Query time: 70 msec
> ;; SERVER: 8.8.4.4#53(8.8.4.4)
> ;; WHEN: Thu May 13 10:44:29 EDT 2021
> ;; MSG SIZE rcvd: 54


Jeff

On Thu, May 13, 2021 at 10:41 AM John Cornelius via Outages <
outages@outages.org> wrote:

> Getting reports of issues with Google DNS. Can anyone confirm similar
> issues?
> Location: Kentucky.
>
> _______________________________________________
> Outages mailing list
> Outages@outages.org
> https://puck.nether.net/mailman/listinfo/outages
>

1 2  View All