Simile.amazon.com and business.amazon.com both seem to be working but www.amazon.com<http://www.amazon.com> and amazon.com both are not. Carrier spectrum Wisconsin. Dns seems to be resolving... but have seen a few nxdomains show up from the web browser? Best Regards, Daniel Walters Sr. Systems Engineer. 866.421.2374 ext. 6213 [Omingo Logo] 7625 S Howell Ave, Oak Creek, WI 53154 www.omnigo.com<http://www.omnigo.com/> [cid:image002.png@01D634FD.2F363420][cid:image003.png@01D634FD.2F363420] [cid:image004.png@01D634FD.2F363420]
It’s back now, at least for me. amazon.com <http://amazon.com/> would resolve, but www was cnamed to a broken alias. Was down for about 20 mins, didn’t affect AWS. The strange part - why is amazon using Oracle (Dyn) and Neustar (ultradns) for dns? I’d expect them to trust route53, but I guess redundancy...
On May 28, 2020, at 12:35 PM, Dan Walters via Outages <outages@outages.org> wrote:
Simile.amazon.com and business.amazon.com both seem to be working but www.amazon.com <http://www.amazon.com/> and amazon.com both are not.
Carrier spectrum Wisconsin.
Dns seems to be resolving… but have seen a few nxdomains show up from the web browser?
Best Regards,
Daniel Walters Sr. Systems Engineer. 866.421.2374 ext. 6213 <image001.png> 7625 S Howell Ave, Oak Creek, WI 53154 www.omnigo.com <http://www.omnigo.com/> <image002.png><image003.png> <image004.png>
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Working for me. Florida panhandle. On Thu, May 28, 2020, 2:44 PM Dan Walters via Outages <outages@outages.org> wrote:
Simile.amazon.com and business.amazon.com both seem to be working but www.amazon.com and amazon.com both are not.
Carrier spectrum Wisconsin.
Dns seems to be resolving… but have seen a few nxdomains show up from the web browser?
Best Regards,
Daniel Walters
Sr. Systems Engineer.
*866.421.2374 ext. 6213*
[image: Omingo Logo]
7625 S Howell Ave, Oak Creek, WI 53154
www.omnigo.com
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
It was dig @1.1.1.1 www.amazon.com ; <<>> DiG 9.11.5-P1-1ubuntu2.6-Ubuntu <<>> @1.1.1.1 www.amazon.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 37353 ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1452 ;; QUESTION SECTION: ;www.amazon.com. IN A On Thu, May 28, 2020 at 3:43 PM Dan Walters via Outages <outages@outages.org> wrote:
Simile.amazon.com and business.amazon.com both seem to be working but www.amazon.com and amazon.com both are not.
Carrier spectrum Wisconsin.
Dns seems to be resolving… but have seen a few nxdomains show up from the web browser?
Best Regards,
Daniel Walters
Sr. Systems Engineer.
*866.421.2374 ext. 6213*
[image: Omingo Logo]
7625 S Howell Ave, Oak Creek, WI 53154
www.omnigo.com
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
-- Sincerely, Jason W Kuehl Cell 920-419-8983 jason.w.kuehl@gmail.com
Amazon goofed up their DNS for a bit, the A record for www.amazon.com wasn't there and the raw amazon.com was redirecting to www. Some discussion on HN: https://news.ycombinator.com/item?id=23341170 On Thu, May 28, 2020 at 3:49 PM Dan Walters via Outages <outages@outages.org> wrote:
Simile.amazon.com and business.amazon.com both seem to be working but www.amazon.com and amazon.com both are not.
Carrier spectrum Wisconsin.
Dns seems to be resolving… but have seen a few nxdomains show up from the web browser?
Best Regards,
Daniel Walters
Sr. Systems Engineer.
*866.421.2374 ext. 6213*
[image: Omingo Logo]
7625 S Howell Ave, Oak Creek, WI 53154
www.omnigo.com
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
On Thu, May 28, 2020 at 07:35:10PM +0000, Dan Walters via Outages wrote:
Simile.amazon.com and business.amazon.com both seem to be working but www.amazon.com<http://www.amazon.com> and amazon.com both are not.
Carrier spectrum Wisconsin.
Dns seems to be resolving... but have seen a few nxdomains show up from the web browser?
Results from one authoritative amazon.com server shown below; similar results for the others.
dig +short NS amazon.com ns2.p31.dynect.net. pdns6.ultradns.co.uk. ns3.p31.dynect.net. ns4.p31.dynect.net. ns1.p31.dynect.net. pdns1.ultradns.net.
dig @ns2.p31.dynect.net www.amazon.com
;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 43669 ;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;www.amazon.com. IN A ;; ANSWER SECTION: www.amazon.com. 1800 IN CNAME tp.47cf2c8c9-frontier.amazon.com.
dig @ns2.p31.dynect.net tp.47cf2c8c9-frontier.amazon.com.
;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39568 ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 4, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;tp.47cf2c8c9-frontier.amazon.com. IN A One of my caches has: www.amazon.com. 1793 IN CNAME tp.47cf2c8c9-frontier.amazon.com. tp.47cf2c8c9-frontier.amazon.com. 53 IN CNAME www.amazon.com.edgekey.net. www.amazon.com.edgekey.net. 3575 IN CNAME e15316.e22.akamaiedge.net. e15316.e22.akamaiedge.net. 13 IN A 23.10.134.216 This has been going on longer than 53 seconds, so apparently sometimes the authoritative servers are able to resolve the "tp..." name. -- Brett
dan.walters> Simile.amazon.com and business.amazon.com both seem to be dan.walters> working but [[www.amazon.com]] and amazon.com both are not. I was debugging as it was coming back up. It looks like a failure somewhere in the CNAME chain from AWS to akamaiedge. Initial CNAME on ultradns worked, it broke a couple of steps further. jlk> The strange part - why is amazon using Oracle (Dyn) and Neustar jlk> (ultradns) for dns? I'd expect them to trust route53, but I guess jlk> redundancy... DDoS/redundancy for the entrance to the CNAME chain, would be my guess.
participants (7)
-
Brett Frankenberger -
Dan Walters -
Jason Kuehl -
John Kinsella -
Lyall Kress -
Paul Ebersman -
Sean Harlow