Massive Dyn DNS outage • Hacker News Board

Re: Massive Dyn DNS outage

#101

Post by [deleted] » Fri, Oct 21, 2016, 1:35 PM UTC

benhoyt wrote: post #21

mikemcquaid wrote: post #8

GitHub 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?

[deleted]

Re: Massive Dyn DNS outage

#102

Post by gianarb » Fri, Oct 21, 2016, 1:44 PM UTC

http://downdetector.com/status/level3/map/

Re: Massive Dyn DNS outage

#103

Post by FartyBumMcPoops » Fri, Oct 21, 2016, 1:55 PM UTC

i have highly available biscuits

Re: Massive Dyn DNS outage

#104

Post by FartyBumMcPoops » Fri, Oct 21, 2016, 1:55 PM UTC

i have highly available biscuits

Re: Massive Dyn DNS outage

#105

Post by danseasner » Fri, Oct 21, 2016, 1:57 PM UTC

Wiki leaks news held back all day for the most part the 20th. Clinton mafia attack. Had diplo,Ativan dinner in n y. Last night

Re: Massive Dyn DNS outage

#106

Post by danseasner » Fri, Oct 21, 2016, 1:59 PM UTC

Xclinton hack. News held back the 20th through 12 n 13th dump. Was a diplomatic dinner last night in n y c I live on east coast n e c

Re: Massive Dyn DNS outage

#107

Post by Avalanchee » Fri, Oct 21, 2016, 2:02 PM UTC

LinkedIn?

Re: Massive Dyn DNS outage

#108

Post by Avalanchee » Fri, Oct 21, 2016, 2:05 PM UTC

Linkedin doesn't seem to load page's contents as well.

Re: Massive Dyn DNS outage

#109

Post by cylinder » Fri, Oct 21, 2016, 2:16 PM UTC

jtmarmon wrote: post #9

mikemcquaid wrote: post #8

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

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

#110

Post by tuke » Fri, Oct 21, 2016, 2:24 PM UTC

6d6b73 wrote: post #48

ljosa wrote: post #37

Earlier quoted context omitted.

The TTL for the glue records of a .com domain is 48 hours, so even if you have Route53 set up and ready to go, it takes a long time to switch the zone away from Dyn. We switched from Dyn to Rout53 a few weeks ago. It took about 12 hours before half of the traffic had shifted over.

That's the reason to have your DNS at at least two different companies, working in tandem. In a case where one is down, your Unicorn Corp doesn't go down with it.

N.b., unless things have changed, I don't think Dyn (for one) allows secondary DNS. Maybe that has changed. {?}