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

101–110 of 721 posts

Re: DDoS Attack Against Dyn Managed DNS

#101

Post by nixgeek »

RijilV wrote: post #88
ljosa wrote: post #52

Earlier quoted context omitted.

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?

Not sure if people are confusing Amazon with AWS in this case.

$ dig +short ns amazon.com

ns1.p31.dynect.net. pdns1.ultradns.net. ns4.p31.dynect.net. pdns6.ultradns.co.uk. ns3.p31.dynect.net. ns2.p31.dynect.net.

Re: DDoS Attack Against Dyn Managed DNS

#102

Post by alberts00 »

afshinmeh wrote: post #91
colanderman wrote: post #87

Earlier quoted context omitted.

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

yup, that's what I meant. they can use different DNS providers, e.g. route53 AND dyn

Route53 doesn't allow using it as slave DNS. https://forums.aws.amazon.com/thread.jspa?threadID=56011

Re: DDoS Attack Against Dyn Managed DNS

#104

Post by lanna »

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…

This is what you can do to restore your GitHub access:

    grep github ~/.ssh/known_hosts
    sudo vim /etc/hosts
    sudo killall -HUP mDNSResponder
    ping github.com

Re: DDoS Attack Against Dyn Managed DNS

#105

Post by dspillett »

owenwil wrote: post #24
olegkikin wrote: post #20

Earlier quoted context omitted.

They all work fine for me.

Caching is a magical thing :)

If anycast routing is in play, which is not unlikely with a DNS service like that, then it may also be that specific servers are being attacked so the outages don't affect users in all locations as some will be routed to infrastructure that is not affected.

Re: DDoS Attack Against Dyn Managed DNS

#106

Post by wongarsu »

jtmarmon wrote: 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

All of these work for me from Germany, and querying their authorative nameservers works just fine (so definitely no caching effect). Anycast for the win!

Re: DDoS Attack Against Dyn Managed DNS

#107

Post by wongarsu »

ilostmykeys wrote: post #54

The Internet is so resilient. LOLz.

The internet is resilient against being completely taken down (as demonstrated by everything working just fine for me from Germany). It's explicitly not resilient against taking parts of it down. You can take some continents off the internet entirely by cutting half a dozend cables, but it's extremely hard to make the internet unusable for everyone.

Re: DDoS Attack Against Dyn Managed DNS

#108

Post by [deleted] »

cddotdotslash wrote: post #79
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…

I'm curious why you don't host your status page on a different domain/provider? When checking this AM why GitHub was down, I also couldn't reach the status page.

[deleted]

Re: DDoS Attack Against Dyn Managed DNS

#109

Post by wongarsu »

dijit wrote: post #60
altyus wrote: post #36

For me redirecting my DNS to Google public DNS 8.8.8.8 and 8.8.4.4 did the trick.

that's not going to help much if the authoritative name servers (which is what dyn is, btw) go down for more than a day. Max record cache time is 86400s (24h), so if the attackers can keep it down for 24h then google will have to have custom instructions in place (or cache more aggressively than the RFC allows)

Since the attacked dyndns DNS servers are evidently anycast, the google server you are reaching might connect to a different dyndns server than you do. If google has luck to reach a less overloaded server, they might get an answer where you get none.

Re: DDoS Attack Against Dyn Managed DNS

#110

Post by jtmarmon »

scrollaway wrote: post #100
jtmarmon wrote: post #81

Earlier quoted context omitted.

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

So, yes. https://github.com/robbyrussell/oh-my-zsh/wiki/Plugins#githu... oh-my-zsh is, imho, way overengineered and bloated. Leads to all sorts of issues like the one you're encountering there. I would recommend sticking to a plain zshrc file that you can read, edit and fully understand. The one I wrote and am using day to day is available here, with documentation: https://github.com/jleclanche/dotfiles

removed the github plugin, reloaded zsh and happened again 5 min later. I believe it has to do with slack, because the issue resolved itself after closing. maybe slack got pwned and all slack users are being used as part of the botnet lol
Post reply on HN