Massive Dyn DNS outage
261–270 of 302 posts
Re: Massive Dyn DNS outage
#262Anyone with an app affected by this because you use Heroku's SSL endpoint can fix this by switching to SNI. Unfortunately Heroku's API is also affected. There is a workaround... just edit your hosts file to point to the proper ip addresses temporarily. add 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 --ty…
edit: apparently SNI isn't supported on legacy dynos.
Re: Massive Dyn DNS outage
#263Sendgrid support page is down as well https://support.sendgrid.com/hc/en-us
Re: Massive Dyn DNS outage
#264GitHub employee here. We're monitoring an incident with our upstream DNS provider: https://twitter.com/githubstatus/status/789433336083001344
Can we add a line to our /etc/hosts file with a hard-coded DNS entry to fix it in the meantime? What's the IP address?
199.16.156.70 twitter.com
104.244.43.231 abs.twimg.com
104.244.43.231 pbs.twimg.com
192.30.253.113 github.com
151.101.24.133 assets-cdn.github.com
Re: Massive Dyn DNS outage
#265Same idea, just add the IPs to your hosts file.
Re: Massive Dyn DNS outage
#266Amazon and Spotify are still up.
Re: Massive Dyn DNS outage
#267Re: Massive Dyn DNS outage
#268Re: Massive Dyn DNS outage
#269http://www.dailydot.com/layer8/how-to-change-dns-settings-ma...
Re: Massive Dyn DNS outage
#270Twitter, Github, Quora, Soundcloud, Etsy, PayPal, Heroku, The Guardian, WhatsApp and numerous others still down as of 1:00 pm PT. Amazon and Spotify are still up.