[outages] Google DNS

[Damian Menscher]

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 at 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 at 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 at 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/outages/attachments/20131206/b715fa3f/attachment.htm>