[outages] Google 8.8.8.8 Resolution of Route53 domains

[Phil Lavin]

This doesn’t feel right, though I’ll admit I’ve never checked before. Our only route to ns-163.awsdns-20.com (205.251.192.163) is through HE:
inet.0: 757581 destinations, 2107440 routes (757301 active, 0 holddown, 522 hidden)
+ = Active Route, - = Last Active, * = Both
205.251.192.0/24   *[BGP/170] 01:12:08, localpref 70
                      AS path: 6939 10297 I, validation-state: unverified
                    > to 216.66.90.21 via ge-1/0/5.0
AS10297 is eNET inc. Is this expected?

From: Outages <outages-bounces at outages.org> On Behalf Of Phil Lavin via Outages
Sent: 24 April 2018 13:04
To: outages at outages.org
Subject: Re: [outages] Google 8.8.8.8 Resolution of Route53 domains

Looks more specific to AWS than it does to Google+AWS. Can’t resolve against some of AWS’s NS directly:
phil at phil-debian:~$ dig cloudcall.com IN A @ns-163.awsdns-20.com
; <<>> DiG 9.10.3-P4-Debian <<>> cloudcall.com IN A @ns-163.awsdns-20.com
;; global options: +cmd
;; connection timed out; no servers could be reached

From: Outages <outages-bounces at outages.org<mailto:outages-bounces at outages.org>> On Behalf Of Phil Lavin via Outages
Sent: 24 April 2018 12:56
To: outages at outages.org<mailto:outages at outages.org>
Subject: Re: [outages] Google 8.8.8.8 Resolution of Route53 domains

Yeh. Still digging into it.

From: Outages <outages-bounces at outages.org<mailto:outages-bounces at outages.org>> On Behalf Of Zach Hanna via Outages
Sent: 24 April 2018 12:54
To: outages at outages.org<mailto:outages at outages.org>
Subject: [outages] Google 8.8.8.8 Resolution of Route53 domains

Anyone else seeing SERVFAIL for route53-hosted domains trying to resolve with Google DNS?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/outages/attachments/20180424/82c995bc/attachment.htm>