Anyone else having problems resolving DNS from UltraDNS? I'm seeing this: $ dig www.ultradns.com @8.8.8.8 ; <<>> DiG 9.6.0-P1 <<>> www.ultradns.com @8.8.8.8 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 26650 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;www.ultradns.com. IN A ;; Query time: 38 msec ;; SERVER: 8.8.8.8#53(8.8.8.8) ;; WHEN: Wed Dec 23 16:59:39 2009 ;; MSG SIZE rcvd: 34 $ dig www.ultradns.com +trace ;; Truncated, retrying in TCP mode. ; <<>> DiG 9.6.0-P1 <<>> www.ultradns.com +trace ;; global options: +cmd . 490316 IN NS d.root-servers.net. . 490316 IN NS k.root-servers.net. . 490316 IN NS j.root-servers.net. . 490316 IN NS h.root-servers.net. . 490316 IN NS g.root-servers.net. . 490316 IN NS m.root-servers.net. . 490316 IN NS c.root-servers.net. . 490316 IN NS i.root-servers.net. . 490316 IN NS b.root-servers.net. . 490316 IN NS e.root-servers.net. . 490316 IN NS a.root-servers.net. . 490316 IN NS l.root-servers.net. . 490316 IN NS f.root-servers.net. . 490316 IN NS d.root-servers.net. . 490316 IN NS k.root-servers.net. . 490316 IN NS j.root-servers.net. . 490316 IN NS h.root-servers.net. . 490316 IN NS g.root-servers.net. . 490316 IN NS m.root-servers.net. . 490316 IN NS c.root-servers.net. . 490316 IN NS i.root-servers.net. . 490316 IN NS b.root-servers.net. . 490316 IN NS e.root-servers.net. . 490316 IN NS a.root-servers.net. . 490316 IN NS l.root-servers.net. . 490316 IN NS f.root-servers.net. ;; Received 717 bytes from 10.23.69.254#53(10.23.69.254) in 52 ms com. 172800 IN NS C.GTLD-SERVERS.NET. com. 172800 IN NS A.GTLD-SERVERS.NET. com. 172800 IN NS G.GTLD-SERVERS.NET. com. 172800 IN NS I.GTLD-SERVERS.NET. com. 172800 IN NS D.GTLD-SERVERS.NET. com. 172800 IN NS E.GTLD-SERVERS.NET. com. 172800 IN NS B.GTLD-SERVERS.NET. com. 172800 IN NS J.GTLD-SERVERS.NET. com. 172800 IN NS K.GTLD-SERVERS.NET. com. 172800 IN NS H.GTLD-SERVERS.NET. com. 172800 IN NS F.GTLD-SERVERS.NET. com. 172800 IN NS L.GTLD-SERVERS.NET. com. 172800 IN NS M.GTLD-SERVERS.NET. ;; Received 522 bytes from 192.228.79.201#53(b.root-servers.net) in 70 ms ultradns.com. 172800 IN NS pdns1.ultradns.net. ultradns.com. 172800 IN NS pdns2.ultradns.net. ultradns.com. 172800 IN NS pdns3.ultradns.org. ultradns.com. 172800 IN NS pdns4.ultradns.org. ultradns.com. 172800 IN NS pdns5.ultradns.info. ultradns.com. 172800 IN NS pdns6.ultradns.co.uk. ;; Received 237 bytes from 192.52.178.30#53(K.GTLD-SERVERS.NET) in 374 ms ;; connection timed out; no servers could be reached
Mark Pace wrote:
Anyone else having problems resolving DNS from UltraDNS?
I'm seeing this:
$ dig www.ultradns.com @8.8.8.8
Yeah, they went belly up in the last 20 or so. Hard. Looks like it's hitting some of Amazon's Cloud stuff too. It seems west coast related, by the way. -- Oh, mairzy doats and dozy doats and liddle lamzy divey A kiddley divey too, wooden chu? Three little fiddies in an iddy, bitty pooh, Three little fiddies and a mama fiddy too...
Anyone else having problems resolving DNS from UltraDNS?
I'm seeing this:
$ dig www.ultradns.com @8.8.8.8
Yeah, they went belly up in the last 20 or so. Hard. Looks like it's hitting some of Amazon's Cloud stuff too. It seems west coast related, by the way.
On the west coast here. They went at 4:44pm (Pacific). pace
Anyone else having problems resolving DNS from UltraDNS?
I'm seeing this:
$ dig www.ultradns.com @8.8.8.8
Yeah, they went belly up in the last 20 or so. Hard. Looks like it's hitting some of Amazon's Cloud stuff too. It seems west coast related, by the way.
On the west coast here. They went at 4:44pm (Pacific).
Recovered at this point... pace
Clarification: www.ultradns.com is back. There are still other problems afoot, like amazon: $ dig amazon.com @8.8.8.8 ; <<>> DiG 9.6.0-P1 <<>> amazon.com @8.8.8.8 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 56390 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;amazon.com. IN A ;; Query time: 2042 msec ;; SERVER: 8.8.8.8#53(8.8.8.8) ;; WHEN: Wed Dec 23 17:28:10 2009 ;; MSG SIZE rcvd: 28 On 12/23/2009 5:22 PM, Mark Pace wrote:
Anyone else having problems resolving DNS from UltraDNS?
I'm seeing this:
$ dig www.ultradns.com @8.8.8.8
Yeah, they went belly up in the last 20 or so. Hard. Looks like it's hitting some of Amazon's Cloud stuff too. It seems west coast related, by the way.
On the west coast here. They went at 4:44pm (Pacific).
Recovered at this point...
pace
Mark Pace wrote:
Anyone else having problems resolving DNS from UltraDNS?
I'm seeing this:
$ dig www.ultradns.com @8.8.8.8
Yeah, they went belly up in the last 20 or so. Hard. Looks like it's hitting some of Amazon's Cloud stuff too. It seems west coast related, by the way.
On the west coast here. They went at 4:44pm (Pacific).
Recovered at this point...
Not from Seattle WA via Comcast HSI: jsage@spunky:$ dig www.ultradns.com @8.8.8.8 ; <<>> DiG 9.6.1-P2 <<>> www.ultradns.com @8.8.8.8 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 21733 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;www.ultradns.com. IN A ;; Query time: 65 msec ;; SERVER: 8.8.8.8#53(8.8.8.8) ;; WHEN: Wed Dec 23 17:29:41 2009 ;; MSG SIZE rcvd: 34 Also images on my web site are not loading from s3.amazonaws.com - John
I'm still seeing the DNS servers at udns down, hard. Amazon's cloud will need a reboot when this is over. Dang, what the heck happened to all that anycast stuff?
On Wed, Dec 23, 2009 at 05:38:21PM -0800, Shrdlu wrote:
I'm still seeing the DNS servers at udns down, hard. Amazon's cloud will need a reboot when this is over. Dang, what the heck happened to all that anycast stuff?
We have some DNS providing type customers (not UltraDNS) receiving a few million packets/sec of UDP/53 DoS traffic, starting at about the same time as the UltraDNS problems. No clue if it's related, but it certainly sounds suspicious. :) -- Richard A Steenbergen <ras@e-gerbil.net> http://www.e-gerbil.net/ras GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC)
Richard A Steenbergen wrote:
On Wed, Dec 23, 2009 at 05:38:21PM -0800, Shrdlu wrote:
I'm still seeing the DNS servers at udns down, hard. Amazon's cloud will need a reboot when this is over. Dang, what the heck happened to all that anycast stuff?
We have some DNS providing type customers (not UltraDNS) receiving a few million packets/sec of UDP/53 DoS traffic, starting at about the same time as the UltraDNS problems. No clue if it's related, but it certainly sounds suspicious. :)
I saw close to a hundred hits on my local dns servers for one request, and they were mostly due to the crazy amazon cloud stuff. You looking at the packets? -- Oh, mairzy doats and dozy doats and liddle lamzy divey A kiddley divey too, wooden chu? Three little fiddies in an iddy, bitty pooh, Three little fiddies and a mama fiddy too...
participants (4)
-
John Sage -
Mark Pace -
Richard A Steenbergen -
Shrdlu