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

Massive Dyn DNS outage

news.ycombinator.com

Post reply on HN
Print view View original

111–120 of 302 posts

Re: Massive Dyn DNS outage

#113

Post by dg123r »

And aws: 6:13 AM PDT [RESOLVED] Between 4:31 AM and 6:10 AM PDT, we experienced errors resolving the DNS hostnames used to access some AWS services in the US-EAST-1 Region. During the issue, customers may have experienced failures indicating "hostname unknown" or "unknown host exception" when attempting to resolve the hostnames for AWS services and EC2 instances. This issue has been resolved and the service is operating normally.

Re: Massive Dyn DNS outage

#114

Post by a3n »

bhaak wrote: post #38
6d6b73 wrote: post #32

All this talk about redundancy, real-time apps, scalable architecture and and a "simple" DDOS against DNS architecture brings half of the internet down. Honestly did nobody think about having a spare dns at some other company? or even backup dns server exactly for a situation like that?

From where I'm looking at the internet (central Europe), I don't notice anything. Maybe your internet on the other side of the Atlantic is broken, ours seems to be working fine. ;-) Edit: Looks like the eastern part of the USA is affected: https://cloudharmony.com/status-for-dyn

> Maybe your internet on the other side of the Atlantic is broken, ours seems to be working fine. ;-)

Works on my continent.

Re: Massive Dyn DNS outage

#118

Post by mohsinr »

alfalfasprout wrote: post #12
mikemcquaid wrote: post #8

GitHub employee here. We're monitoring an incident with our upstream DNS provider: https://twitter.com/githubstatus/status/789433336083001344

Hahahahaha you do realize Twitter is one of the affected sites, right?

Exactly, I see tweet in Google SERPS for GitHub , I try to access and twitter too is down like Github.

Re: Massive Dyn DNS outage

#119

Post by mancerayder »

6d6b73 wrote: post #32

All this talk about redundancy, real-time apps, scalable architecture and and a "simple" DDOS against DNS architecture brings half of the internet down. Honestly did nobody think about having a spare dns at some other company? or even backup dns server exactly for a situation like that?

If ONLY they had 10X developers ...

EDIT: joking aside, the issue with multiple DNS providers is primarily (in my experience at the company I'm at having investigated this in the past) intelligent DNS entries. Example, 'return these A records, in this order, based on the number of requests, roughly balanced'.

There's no universal standard, just common aspects. DNS Provider A has one set of features, names for returning A records in some way, based on some weighted averaging, provider B has a different mechanism. So as an infrastructure person you have to:

1. Investigate provider A and B features for intelligent DNS (it's not even universally called intelligent DNS!), and mentally parse the commonalities and differences

2. Create a custom mechanism to keep them in sync internally. So you hope that A and B have an API for maintaining the records.

3. Ensure that when someone in your org wants to make an update, A and B update at the same time in the same way

4. APIs don't change.

Post reply on HN