Live data from Hacker News

DDoS Attack Against Dyn Managed DNS

dynstatus.com

61–70 of 721 posts

Re: DDoS Attack Against Dyn Managed DNS

#61
post #37

Earlier quoted context omitted.

Most of this stuff you should have locally, and not depend on 3rd party websites.

I'm so damn tired of the "host it locally" mentality. Not everyone has the resources to host all of that locally. For example, most open source projects. But even outside of that, we use github for issue tracking, the new project management kanban stuff, a CI server, reading documentation (which is offline, but the online versions are nicer on the eyes), and a ton more. Not to mention that StackOverflow and other dis…

And I'm so damn tired of people complaining about cost to run stuff locally. The true cost of not having some basic stuff setup locally, even for backup purposes is when situation like this happens. It does not take long time or resources to download all of the libraries, with corresponding docs to a local server, or even your laptop. It is not complicated to have all of the new issues sent to an email to have a version of them available at all times. And you don't need a sysadmin to administer all of that.

Re: DDoS Attack Against Dyn Managed DNS

#67
post #4

I'm updating a list of confirmed outages as I see them here https://news.ycombinator.com/item?id=12759520 So far twitter, etsy, soundcloud, spotify, github, pagerduty...crazy that this can even happen

I'm surprised; I would have thought such large sites would use more than one DNS provider? I mean:

    $ host -t NS twitter.com
    twitter.com name server ns4.p34.dynect.net.
    twitter.com name server ns3.p34.dynect.net.
    twitter.com name server ns2.p34.dynect.net.
    twitter.com name server ns1.p34.dynect.net.
I would have expected at least one of those to be somewhere else. What is the reason they would not have a backup provider?

Re: DDoS Attack Against Dyn Managed DNS

#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 people are having problems resolving Twitter domains as well.

Post reply on HN