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

111–120 of 721 posts

Re: DDoS Attack Against Dyn Managed DNS

#111

Post by ToastyMallows »

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.

+1

The only way that I could check to see if Github knew they were having problems was by searching Google for "github status", and then seeing from the embedded Twitter section in the results page that there was a tweet about having problems. Twitter also being down for me didn't help the situation either.

Re: DDoS Attack Against Dyn Managed DNS

#112

Post by nkozyra »

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?

If that were the reason I wouldn't expect this update:

6:36 AM PDT [RESOLVED] Between 4:31 AM and 6:10 AM PDT, we experienced errors resolving the DNS hostnames used to access some AWS services in the US-EAST-1 Region. During the issue, customers may have experienced failures indicating "hostname unknown" or "unknown host exception" when attempting to resolve the hostnames for AWS services and EC2 instances. This issue has been resolved and the service is operating normally.

Re: DDoS Attack Against Dyn Managed DNS

#113

Post by 6d6b73 »

tobz wrote: post #99
6d6b73 wrote: post #61

Earlier quoted context omitted.

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 vers…

This is a DNS outage. If self-hosted, somewhere, you could still be screwed by having Dyn as your DNS provider. If dev-machine-hosted, then uh, your issue tracker is no longer an issue tracker. Your build server is not a build server. All the services besides Git are not meant to operate offline in a decentralized/distributed fashion. Library documentation, sure, that could be local. Otherwise, your assertion that al…

First of all I'm not saying that the whole infrastructure could be replicated, only critical parts, and parts that can be easily hosted locally.

Second, pointing to a new machine is as simple as updating IP in your hosts file, or dns server.

Third, you can use vmware or any other virtualization stack to replicate your infrastructure locally. In fact that's the best way to build things - create virtual network, use it for testing, troubleshooting and debugging, and deploy only when everything is working.

All I'm saying is that if you're company is making any kind of money, and your development environment depends 100% on online services, you're doing it wrong.

Re: DDoS Attack Against Dyn Managed DNS

#116

Post by dijit »

redm wrote: post #51
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 sell premium services, have a large sales team, and are very aggressive. I get emails from them weekly discussing millisecond savings of their DNS solutions and the value increase in customers and sales. Squeaky wheels get grease and their sales team squeaks a lot.

Realistically they compete with Neustar which is shockingly expensive and has less features and is harder to use.

I chose Dyn over Neustar (UltraDNS) when it was time to renew contracts because it was 60% cheaper, had a better latency, their support was great and the interfaces were clear.

Not a fanboy or anything, I really don't like how aggressively they hound me now (even though I have nothing to do with DNS for my current employer), but it's cheap and effective so it's not surprising people use them.

Re: DDoS Attack Against Dyn Managed DNS

#117

Post by lanna »

lanna wrote: post #104
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

Why am I being downvoted for providing useful information? I don't understand HN...

Re: DDoS Attack Against Dyn Managed DNS

#118

Post by detaro »

owenwil wrote: post #15
bananicorn wrote: post #12

Earlier quoted context omitted.

Weird, works for me - from Italy (not sure if there isn't just some caching going somewhere down the line and I can see it because of that) edit: nevermind, it's almost certain i've got it cached

Definitely a DNS cache on your computer (Or even in Chrome)

I can query the authoritative ns*.p16.dynect.com DNS servers from Europe (Germany in my case), and the traceroute looks like it's near Frankfurt. So the anycasted copies here seem fine.

Re: DDoS Attack Against Dyn Managed DNS

#119

Post by pyvpx »

alberts00 wrote: post #102
afshinmeh wrote: post #91

Earlier quoted context omitted.

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

more accurately, they don't support the common standard methodologies for transferring zone data between primary and secondary name servers (like NOTIFY, AXFR, etc).

there is nothing stopping you from having Route53 and $others as NS records for your domains. You just have to make sure they stay consistent. Apparently from the linked discussion, there are people offering scripts and services to do just that.

Re: DDoS Attack Against Dyn Managed DNS

#120

Post by pyvpx »

dijit wrote: post #116
redm wrote: post #51

Earlier quoted context omitted.

They sell premium services, have a large sales team, and are very aggressive. I get emails from them weekly discussing millisecond savings of their DNS solutions and the value increase in customers and sales. Squeaky wheels get grease and their sales team squeaks a lot.

Realistically they compete with Neustar which is shockingly expensive and has less features and is harder to use. I chose Dyn over Neustar (UltraDNS) when it was time to renew contracts because it was 60% cheaper, had a better latency, their support was great and the interfaces were clear. Not a fanboy or anything, I really don't like how aggressively they hound me now (even though I have nothing to do with DNS for m…

they are cheap compared to Neustar. And Neustar is priced like a Bugatti. Dyn is more Porsche pricing.
Post reply on HN