Live data from Hacker News

DDoS Attack Against Dyn Managed DNS

dynstatus.com

281–290 of 721 posts

Re: DDoS Attack Against Dyn Managed DNS

#281
post #120

Earlier quoted context omitted.

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

Way, way back in time, they offered lifetime DNS hosting for a relatively low price. I bought that, and they've honored the deal. Admittedly it comes with limits that would make it useless for any large site, but it's just great for individuals.

I have a similar deal with UltraDNS. Nice to have "enterprise" DNS for my little personal sites.

Re: DDoS Attack Against Dyn Managed DNS

#283
post #214

Out of curiosity, why do caching DNS resolvers, such as the DNS resolver I run on my home network, not provide an option to retain last-known-good resolutions beyond the authority-provided time to live? In such a configuration, after the TTL expiration, the resolver would attempt to refresh from the authority/upstream provider, but if that attempt fails, the response would be a more graceful failure of returning a la…

I've been thinking of adding this exact feature to my DNS framework that I've been working on (if github was resolving): https://github.com/bluejekyll/trust-dns If you have any feedback, I'd love to hear it.

Sounds promising. I'll want to take a look when GitHub is resolvable again. :)

Re: DDoS Attack Against Dyn Managed DNS

#285

Any quick script to see if a given domain ultimately resolves to them? My SaaS company has a lot of custom domains from whatever DNS servers pointed at us and I'd like to be able to tell people whether it's our fault or not.

`dig NS $domain`

Query for the root domain, without any subdomains like www. That is, you need to check the "zone apex," the shortest name purchased from a registrar and potentially delegated to Dyn. Look for dynect.net in the list of authoritative name servers.

Re: DDoS Attack Against Dyn Managed DNS

#287
I've been singing the praise of AWS Route53 for a long time, they up and running. I can't believe major multi-million dollar companies (Twitter, GitHub, Soundcloud, Pagerduty) would not run a mix of multiple DNS providers.

Also what is happening is a cascade effect, where a 3rd party being down effects others.

Re: DDoS Attack Against Dyn Managed DNS

#288
post #243

Earlier quoted context omitted.

All will break the moment that one of the websites that you access makes a server-side request to another website ( think about logging-services, server-clusters, database servers, etc - they all either have IPs or most-likely some domains. )

I'm not sure I understand what you're saying. The scenario is that my local network's caching DNS resolver retains resolutions beyond the authority-provided TTL in the event that a TTL-specified refresh at expiration fails. Therefore, my web browser may—in the very rare situation where this arises—make an HTTP request to an IP address of a server that has been intentionally moved by a service provider (let's assume t…

One possible issue is that IPs are re-used in cloud environments. Potentially, your browser could POST sensitive data to an IP address that now belongs to a totally different company.

Re: DDoS Attack Against Dyn Managed DNS

#290
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 love how the White House & GH posted a statement on Twitter.. that we can't access since its down.

Twitter's working fine for me. This attack is affecting different people differently; as a DDOS, attacking a distributed system (DNS) with a lot of redundancy, it's possible for some people to be affected badly while others not affected at all.

I briefly lost access to GitHub, but Twitter has been working fine every time I've checked. Posting status messages in multiple venues helps to ensure that even if one channel is down, people might be able to get status from another channel.

Post reply on HN