I thought DNS (particularly public) was basically immune to DDoS? If one DNS server is down, use the cached result or another server. DNS is some of the most distributable, cachable data I can imagine.
Seriously, please someone explain this. I thought DNS info is propagated among DNS servers, and it is cached on all of them... How can an attack to a single DNS company cause this outage??
Massive Dyn DNS outage
281–290 of 302 posts
Re: Massive Dyn DNS outage
#282All 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?
Maybe it is time to widely adopt namecoin ?
For those interested: https://namecoin.org/
Re: Massive Dyn DNS outage
#283- to deploy to Heroku
174.129.22.147 git.heroku.com
- to enable Twitter from Web 104.244.42.65 twitter.com
93.184.220.70 pbs.twimg.com
104.244.43.7 o.twimg.com
- to access Github (as another poster wrote): 192.30.253.113 github.com
151.101.4.133 assets-cdn.github.com
You can find any other IPs you need on sites like http://www.hcidata.info/host2ip.cgiJust remember to rollback your hosts file after the outage finishes.
Re: Massive Dyn DNS outage
#284Earlier quoted context omitted.
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
I'm in Las Vegas and I haven't had access to several sites all day. I don't think this is limited to eastern U.S.
Re: Massive Dyn DNS outage
#285Re: Massive Dyn DNS outage
#286Re: Massive Dyn DNS outage
#287-Jason (5:13 PM EDT; 21:13 UTC)