Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Amazon DNS error

amazon.com

Post reply on HN
Print view View original

41–50 of 71 posts

Re: Amazon DNS error

#44

Post by robryan »

I wonder if we should except s3 to degrade pretty badly if this isn't fixed soon. Going to be seeing a much higher than normal rate of requests.

Re: Amazon DNS error

#45

Post by anonymuse »

anonymuse wrote: post #33

AWS Status shows Cloudfront DNS issues, which is reflected in our page's assets not loading. Kinda makes me wish we were using something like https://github.com/etsy/cdncontrol/ but that's a fight for another day! Informational message: DNS Resolution errors http://status.aws.amazon.com Wed, 26 Nov 2014 17:00:39 PST http://status.aws.amazon.com/#cloudfront_1417050039 We are currently investigating increased error rat…

Anecdotally, our site is now loading quickly for me: http://canary.is/.

However, digging the Cloudfront name servers times out intermittently:

  $ dig +short @ns-666.awsdns-19.net cloudfront.net
  ;; connection timed out; no servers could be reached

Re: Amazon DNS error

#46

Post by rdl »

I'm curious if the root cause of this is software failure or external attack. Aws is clearly at the point in size and competence that hardware failures are unlikely as root cause.

Re: Amazon DNS error

#47

Post by jdotjdot »

jordanthoms wrote: post #35
fletchowns wrote: post #30

Earlier quoted context omitted.

Is it any different if you shell out the big bucks for support?

We have business-level support through AWS activate, and it's not any different really - we could submit a ticket and get a phone call back within a 1 hour guarantee, but I'm not sure that would get you much more information or faster resolution for an issue like this. The really big customers presumably have contacts within the AWS team who give them extra information in cases like this.

I had an Urgent-level issue just two days ago (1-hr SLA), also with business-level support through AWS Activate, and it took them THREE hours to get back to me, with me simultaneously waiting on one chat and two phone lines to try to get in contact with anyone I could,

Finally, chat came through--but only after a wait far longer than what their SLA guarantees.

Point being that support probably isn't going to get you much either, especially given that they aren't holding to the 1hr SLA.

Re: Amazon DNS error

#48

Post by lukeschlather »

cjreyes wrote: post #19

Is there a RoR Gem / configuration that will serve assets locally if an external asset host name doesn't resolve or times out?

It's a decent idea, but it would be better to do client-side. For this sort of event, knowing that the name resolves on the server doesn't give you any confidence it will resolve for the client.

What would be really nice is if you could specify a fallback host in your DNS prefetch, and the browser would make it "just work."

Post reply on HN