It is DNS. If you put the EC2/S3 address into /etc/hosts, the services work fine. Affecting lots of other big websites as well apparently (target, salesforce) because they all outsource to UltraDNS
NANOG chatter confirming it is an issue with UltraDNS. Seems to be west coast related.
EDIT: Potentially a DOS attack. From NANOG:
"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 thought DNS was supposed to try backups servers automatically... any DNS experts able to explain what's going on? Some of the ultradns servers are returning (correct) values, others simply not responding.
yeah, uh, if you are smart, you have a secondary DNS provider. But that really requires you managing it yourself. the problem was that many people outsource, which usually means going with only one provider. (now, ultradns does have a good setup, they probably aren't a bad choice for a provider, but having only one is just plain stupid.)
I don't know, I don't think it'd be as much as 4 - 7 days before Christmas. Most people know that it's too late to order from Amazon or any other online-only store by the night of Dec. 23. It's probably more money than they'd lose normally, but maybe not that significant?
I have no data to back that up, it's pure speculation.
Why wouldn't such a company run their own name servers? I understand it's "yet another thing to maintain," but I've set up bind before... didn't seem that bad.
This is one of those services that a dedicated provider can sometimes do better than internal IT. Ultradns, for example, has secure secondaries Colocated with large ISPs so you get some good protection against cache poisoning attacks. Everything they do you could do yourself, but it would cost you a lot more than what they charge. (full disclosure: I am a customer and until this evening I was quite happy with their service and reliability)
It's relatively trivial to outsource. It's one of those services that's easy to measure, quantify, and manage (from an outsourced perspective). There's also a bit more to it then that. The Anycast routing can be quite difficult to setup and maintain. It's virtually useless outside of a very small set of protocols (DNS being one of them), so it wouldn't make sense for Amazon to bring that kind of talent in-house for something like DNS.
[+] [-] cperciva|16 years ago|reply
[+] [-] akl|16 years ago|reply
[+] [-] justinsb|16 years ago|reply
[+] [-] justinsb|16 years ago|reply
[+] [-] shaddi|16 years ago|reply
EDIT: Potentially a DOS attack. From NANOG: "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. :)"
[+] [-] aristus|16 years ago|reply
[+] [-] justinsb|16 years ago|reply
[+] [-] lsc|16 years ago|reply
[+] [-] boredguy8|16 years ago|reply
[+] [-] artagnon|16 years ago|reply
[+] [-] jseifer|16 years ago|reply
[+] [-] ggrot|16 years ago|reply
[+] [-] rlpb|16 years ago|reply
I think the small fry using S3 and EC2 will be the ones who are actually hit by this.
[+] [-] cookiecaper|16 years ago|reply
I have no data to back that up, it's pure speculation.
[+] [-] alain94040|16 years ago|reply
I think my 10% number is too low, so maybe $500K for two minutes? But this is not profit, just revenue.
[+] [-] aw3c2|16 years ago|reply
[deleted]
[+] [-] notmyname|16 years ago|reply
[+] [-] slig|16 years ago|reply
[+] [-] Sam_Odio|16 years ago|reply
EDIT: "No A records were found for amazon.com" http://www.zoneedit.com/lookup.html?host=amazon.com&type...
[+] [-] mattiss|16 years ago|reply
[+] [-] tinio|16 years ago|reply
[+] [-] newhouseb|16 years ago|reply
[+] [-] evgen|16 years ago|reply
[+] [-] rbranson|16 years ago|reply
[+] [-] tybris|16 years ago|reply