Amazon.com and AWS Down For Me, UltraDNS to Blame?

We noticed a bit ago that photos we had stored on Amazon S3 weren’t showing up.  A little digging quickly revealed that things were timing out on DNS resolution for s3.

Looks like they are using UltraDNS as their DNS provider, and UltraDNS looks like it is offline too, at least from here.

Attack, or just really bad luck?

EAS:~ Erik$ dig +trace ultradns.net
; <<>> DiG 9.6.0-APPLE-P2 <<>> +trace ultradns.net
;; global options: +cmd
. 15888 IN NS D.ROOT-SERVERS.NET.
. 15888 IN NS L.ROOT-SERVERS.NET.
. 15888 IN NS G.ROOT-SERVERS.NET.
. 15888 IN NS E.ROOT-SERVERS.NET.
. 15888 IN NS I.ROOT-SERVERS.NET.
. 15888 IN NS M.ROOT-SERVERS.NET.
. 15888 IN NS B.ROOT-SERVERS.NET.
. 15888 IN NS H.ROOT-SERVERS.NET.
. 15888 IN NS C.ROOT-SERVERS.NET.
. 15888 IN NS K.ROOT-SERVERS.NET.
. 15888 IN NS F.ROOT-SERVERS.NET.
. 15888 IN NS A.ROOT-SERVERS.NET.
. 15888 IN NS J.ROOT-SERVERS.NET.
;; Received 228 bytes from 10.210.5.254#53(10.210.5.254) in 45 ms
net. 172800 IN NS D.GTLD-SERVERS.net.
net. 172800 IN NS B.GTLD-SERVERS.net.
net. 172800 IN NS M.GTLD-SERVERS.net.
net. 172800 IN NS E.GTLD-SERVERS.net.
net. 172800 IN NS H.GTLD-SERVERS.net.
net. 172800 IN NS J.GTLD-SERVERS.net.
net. 172800 IN NS F.GTLD-SERVERS.net.
net. 172800 IN NS L.GTLD-SERVERS.net.
net. 172800 IN NS I.GTLD-SERVERS.net.
net. 172800 IN NS K.GTLD-SERVERS.net.
net. 172800 IN NS C.GTLD-SERVERS.net.
net. 172800 IN NS G.GTLD-SERVERS.net.
net. 172800 IN NS A.GTLD-SERVERS.net.
;; Received 499 bytes from 192.36.148.17#53(I.ROOT-SERVERS.NET) in 203 ms
ultradns.net. 172800 IN NS pdns1.ultradns.net.
ultradns.net. 172800 IN NS pdns2.ultradns.net.
ultradns.net. 172800 IN NS pdns3.ultradns.org.
ultradns.net. 172800 IN NS pdns4.ultradns.org.
ultradns.net. 172800 IN NS pdns5.ultradns.info.
ultradns.net. 172800 IN NS pdns6.ultradns.co.uk.
;; Received 221 bytes from 192.48.79.30#53(J.GTLD-SERVERS.net) in 146 ms
;; connection timed out; no servers could be reached
EAS:~ Erik$ dig +trace s3.amazonaws.com
; <<>> DiG 9.6.0-APPLE-P2 <<>> +trace s3.amazonaws.com
;; global options: +cmd
. 15605 IN NS C.ROOT-SERVERS.NET.
. 15605 IN NS F.ROOT-SERVERS.NET.
. 15605 IN NS E.ROOT-SERVERS.NET.
. 15605 IN NS I.ROOT-SERVERS.NET.
. 15605 IN NS A.ROOT-SERVERS.NET.
. 15605 IN NS H.ROOT-SERVERS.NET.
. 15605 IN NS K.ROOT-SERVERS.NET.
. 15605 IN NS J.ROOT-SERVERS.NET.
. 15605 IN NS B.ROOT-SERVERS.NET.
. 15605 IN NS D.ROOT-SERVERS.NET.
. 15605 IN NS L.ROOT-SERVERS.NET.
. 15605 IN NS G.ROOT-SERVERS.NET.
. 15605 IN NS M.ROOT-SERVERS.NET.
;; Received 228 bytes from 10.210.5.254#53(10.210.5.254) in 41 ms
com. 172800 IN NS D.GTLD-SERVERS.NET.
com. 172800 IN NS I.GTLD-SERVERS.NET.
com. 172800 IN NS F.GTLD-SERVERS.NET.
com. 172800 IN NS L.GTLD-SERVERS.NET.
com. 172800 IN NS H.GTLD-SERVERS.NET.
com. 172800 IN NS K.GTLD-SERVERS.NET.
com. 172800 IN NS G.GTLD-SERVERS.NET.
com. 172800 IN NS C.GTLD-SERVERS.NET.
com. 172800 IN NS B.GTLD-SERVERS.NET.
com. 172800 IN NS A.GTLD-SERVERS.NET.
com. 172800 IN NS M.GTLD-SERVERS.NET.
com. 172800 IN NS J.GTLD-SERVERS.NET.
com. 172800 IN NS E.GTLD-SERVERS.NET.
;; Received 506 bytes from 192.33.4.12#53(C.ROOT-SERVERS.NET) in 44 ms
amazonaws.com. 172800 IN NS pdns1.ultradns.net.
amazonaws.com. 172800 IN NS pdns2.ultradns.net.
amazonaws.com. 172800 IN NS pdns3.ultradns.org.
amazonaws.com. 172800 IN NS pdns4.ultradns.org.
amazonaws.com. 172800 IN NS pdns5.ultradns.info.
amazonaws.com. 172800 IN NS pdns6.ultradns.co.uk.
;; Received 237 bytes from 192.43.172.30#53(I.GTLD-SERVERS.NET) in 220 ms
;; connection timed out; no servers could be rea

Leave a Reply

Your email address will not be published. Required fields are marked *