Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

DDoS Attack Against Dyn Managed DNS

dynstatus.com

Post reply on HN
Print view View original

81–90 of 721 posts

Re: DDoS Attack Against Dyn Managed DNS

#81

Post by jtmarmon »

scrollaway wrote: post #77
jtmarmon wrote: post #75

Semi related: I noticed this incident right when it began, but not because I was trying to access a website. This started happening to me: http://imgur.com/PPlaY5o Then when I went to push to github out of fear my computer was about to soil itself, that failed too, and I noticed the outage. Does anyone know if the above errors could be related to the outage? I'm using vim inside tmux with zsh as my shell. Maybe zsh d…

The zsh default git plugin definitely doesn't touch github, or the network in general. Are you using some oh-my-zsh github plugin by any chance?

plugins=(git rbenv nvm gitfast zsh-autosuggestions github)

Re: DDoS Attack Against Dyn Managed DNS

#82

Post by tunap »

artursapek wrote: post #10

Twitter, Reddit, wow. I was so confused for a moment. Thankfully HN is here to explain.

I had several, sporadic 'secure connection could not be established' yesterday while trying to open HN, amongst others. Painfully slow page load times across the board, too(Craigslist, Monoprice,weather.gov, etc) Still may be my buggy phone SIM...

Re: DDoS Attack Against Dyn Managed DNS

#84

Post by cyberferret »

ljosa wrote: post #58

AWS says "We are investigating elevated errors resolving the DNS hostnames used to access some AWS services in the US-EAST-1 Region." Is that coincidental, or are they being DDoSed also?

That might explain why we are down - most of our EC2 instances are in us-east-1. Looks like Amazon SQS is impacted too. We are getting a stream of undeliverable messages, and our 'dead letter' queue is filling up!

Re: DDoS Attack Against Dyn Managed DNS

#85

Post by 3pt14159 »

jssjr wrote: post #68

I'm a GitHub employee and want to let everyone know we're aware of the problems this incident is causing and are actively working to mitigate the impact. "A global event is affecting an upstream DNS provider. GitHub services may be intermittently available at this time." is the content from our latest status update on Twitter ( https://twitter.com/githubstatus/status/789452827269664769 ). Reposted here since some peo…

If this is consistently a problem why doesn't Github have fallback TLDs that use different DNS providers? Or even just code the site to work with static IPs. I tried the Github IP and it didn't load, but that could be for an unrelated issue.

Re: DDoS Attack Against Dyn Managed DNS

#86

Post by colanderman »

ljosa wrote: post #58

AWS says "We are investigating elevated errors resolving the DNS hostnames used to access some AWS services in the US-EAST-1 Region." Is that coincidental, or are they being DDoSed also?

Apparently us-east-1 is backed by Dyn (and only Dyn) as well?

    $ host -t NS us-east-1.amazonaws.com
    us-east-1.amazonaws.com name server ns3.p31.dynect.net.
    us-east-1.amazonaws.com name server ns1.p31.dynect.net.
    us-east-1.amazonaws.com name server ns2.p31.dynect.net.
    us-east-1.amazonaws.com name server ns4.p31.dynect.net.
That's… utterly bizarre to me. us-east-2 has a more diverse selection:

    $ host -t NS us-east-2.amazonaws.com
    us-east-2.amazonaws.com name server u4.amazonaws.com.
    us-east-2.amazonaws.com name server u6.amazonaws.com.
    us-east-2.amazonaws.com name server u3.amazonaws.com.
    us-east-2.amazonaws.com name server u2.amazonaws.com.
    us-east-2.amazonaws.com name server u1.amazonaws.com.
    us-east-2.amazonaws.com name server u5.amazonaws.com.
    us-east-2.amazonaws.com name server ns2.p31.dynect.net.
    us-east-2.amazonaws.com name server ns1.p31.dynect.net.
    us-east-2.amazonaws.com name server pdns1.ultradns.net.
    us-east-2.amazonaws.com name server pdns5.ultradns.info.
    us-east-2.amazonaws.com name server ns3.p31.dynect.net.
    us-east-2.amazonaws.com name server ns4.p31.dynect.net.
    us-east-2.amazonaws.com name server pdns3.ultradns.org.
Not that anyone should be running a service whose availability they care about solely in us-east-1 anyway…

Re: DDoS Attack Against Dyn Managed DNS

#87

Post by colanderman »

pcai wrote: post #80
afshinmeh wrote: post #74

Earlier quoted context omitted.

Just being curious, why don't you use different DNS servers?

Most services, even if they aren't the size of Github, can't change their DNS provider on a dime.

It's not a question of switching; you can host your DNS records at multiple providers.

Re: DDoS Attack Against Dyn Managed DNS

#88

Post by RijilV »

ljosa wrote: post #52
sly010 wrote: post #44

I am confused. Are so many big websites using Dyn, or does Dyn have some special role in the DNS chain in the US?

They're widely used because they were one of the few providers of geo-aware DNS service for a long time. (These days there are other, cheaper options, including Amazon Route53.)

It's pretty wild that AWS is having impacts for the dyn outage given the shoutout to Route53. Wonder what they know that they don't?
Post reply on HN