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

241–250 of 302 posts

Re: Massive Dyn DNS outage

#241

Post by skaw »

rajivm wrote: post #201
jbaviat wrote: post #124

Issue 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

anyone have this info for twitter?

Re: Massive Dyn DNS outage

#242

Post by pamvegas »

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

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

#243

Post by jontodd »

ted_dunning wrote: post #237
jontodd wrote: post #233

It looks like Verizon customers continue to have issues resolving Dyn DNS. Wondering if Verizon has actually blocked Dyn requests

Dyn's status page still says they are working the problem. Why would Verizon block access to a downed service?

Not entirely sure. Perhaps some of the DDOS was flowing through to them but that's complete speculation.

I mostly wanted to throw this out there for others who are trying to segment the impact of the issue.

Re: Massive Dyn DNS outage

#244

Post by GilsonSoares »

Whatsapp too: # host -tns whatsapp.com whatsapp.com name server ns2.p13.dynect.net. whatsapp.com name server ns1.p13.dynect.net. whatsapp.com name server ns4.p13.dynect.net. whatsapp.com name server ns3.p13.dynect.net.

Re: Massive Dyn DNS outage

#249

Post by mej10 »

shuumai wrote: post #240
mej10 wrote: post #228

Earlier quoted context omitted.

Even though their status page says everything is basically fine -- oh just a blip with API dns this morning no biggie -- they have had major problems today too. Like, can't connect to dynamodb, sqs, kinesis. Unfortunately they lie through their status page pretty regularly. I am not sure what it would take for them to admit they had a major problem.

Apparently us-east-1 was the only region that exclusively used dyndns (all other regions have failover strategies to other providers and that's why there wasn't downtime anywhere else but us-east and eu-west). They resolved the problem pretty quickly, but it drove our NOC insane...fortunately downtime for us was only about half an hour or so.

Yeah, thats about a half hour of down time for every AWS East based company... who knows how much lost revenue -- and yet they just say the service is green with a little info tag.

If our service is down for any customer (much less an entire segment of customers) we at least publish that we had a partial outage.

Post reply on HN