Massive Dyn DNS outage
251–260 of 302 posts
Re: Massive Dyn DNS outage
#252Re: Massive Dyn DNS outage
#253Earlier 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
#254Issue came from dynect.net: $ dig +trace github.com ; > DiG 9.8.3-P1 > +trace github.com [...] ;; Received 488 bytes from 192.228.79.201#53(192.228.79.201) in 154 ms github.com. 172800 IN NS ns1.p16.dynect.net. github.com. 172800 IN NS ns3.p16.dynect.net. github.com. 172800 IN NS ns2.p16.dynect.net. github.com. 172800 IN NS ns4.p16.dynect.net. ;; Received 178 bytes from 192.42.93.30#53(192.42.93.30) in 54 ms ;; conne…
If you need access to GitHub, add these to your hosts file: 192.30.253.113 github.com 151.101.4.133 assets-cdn.github.com
Re: Massive Dyn DNS outage
#255Earlier quoted context omitted.
not very useful to post a status update on a site that is experiencing the same issues with the same DNS provider. maybe post a github gist? oh wait...
Should there be a global internet status page at an easily memorizable "vanity" IP address?
Re: Massive Dyn DNS outage
#256I 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.
Re: Massive Dyn DNS outage
#257Re: Massive Dyn DNS outage
#258All 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?
Re: Massive Dyn DNS outage
#259add to /etc/hosts
23.21.149.112 api.heroku.com 107.21.99.123 ssl-doctor.heroku.com
Then use Heroku CLI to switch your app to the new SNI endpoint
heroku certs:add --type sni server.crt server.key -a YOUR_APP
That will spit out a new host name that you can point your DNS to and still be online.