Live data from Hacker News

DDoS Attack Against Dyn Managed DNS

dynstatus.com

641–650 of 721 posts

Re: DDoS Attack Against Dyn Managed DNS

#641

Earlier quoted context omitted.

Trump says he never met Putin, now. In the past, he said he did. I just did a search for "trump met putin" and found a bunch of news sites reporting that in a GOP debate a while ago Trump said “I got to know him very well because we were both on ‘60 Minutes,’ we were stablemates, and we did very well that night.”

Trump was boasting in that debate about nothing, they were on the same episode of 60 minutes but they were not even on the same continent for that episode. http://time.com/4108198/donald-trump-60-minutes-putin/

That's not really the point. The point is Trump is now saying he hasn't, but in the past he said he has. Not only is he contradicting his earlier statement, but it also makes him not trustworthy. And of course, if he was boasting about having supposedly met Putin in the past, that means he thought it was a good thing to boast about, which suggests that he is sympathetic to Putin and to Russian interests.

Re: DDoS Attack Against Dyn Managed DNS

#642

I wanted to provide an update on the PagerDuty service. At this time we have been able to restore the service by migrating to our secondary DNS provider. If you are still experiencing issues reaching any pagerduty.com addresses, please flush your DNS cache. This should restore your access to the service. We are actively monitoring our service and are working to resolve any outstanding issues. We sincerely apologize f…

I had the privilege of being on-call during this entire fiasco today and I have to say I was really really disappointed. It's surprising how broken your entire service was when DNS went down. I couldn't acknowledge anything, and my secondary on-call was getting paged because it looked like I wasn't trying to respond. I was getting phone calls for alerts that wasn't even showing up on the web client, etc. Overall, it…

"It's surprising how broken your entire service was when DNS went down." lol

Re: DDoS Attack Against Dyn Managed DNS

#643
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…

It'd be nice to have a "backup TTL" included, to allow sites to specify whether and how long they wanted such caching behavior. Also, that cache would need to only kick in when the server was unreachable or produced SERVFAIL, not when it returned a negative result. Negative results returned by the authoritative server are correct, and should not result in the recursive resolver returning anything other than a negativ…

It might be a stretch to use the information, but the SOA RR does contain an EXPIRE field, defined as "A 32 bit time value that specifies the upper limit on the time interval that can elapse before the zone is no longer authoritative." It's an additional request, but the SOA RR does contain the type of information you are asking for.

Re: DDoS Attack Against Dyn Managed DNS

#644

Earlier quoted context omitted.

That is not an appropriate tone for someone representing OpenDNS to take.

Why not? It's blunt, but to the point, honest, and passionate. Who cares about tone?

And seems very appropriate for the founder of OpenDNS. Pretty authoritative.

Re: DDoS Attack Against Dyn Managed DNS

#645
post #638
post #272

Earlier quoted context omitted.

Awesome! Is this available as software I can install on my network? Sorry, probably a dumb question.

Yes, but beware, they (at least used to) resolve unknown names to a page filled with ads.

They stopped that.

https://www.opendns.com/no-more-ads/

Re: DDoS Attack Against Dyn Managed DNS

#646

Earlier quoted context omitted.

> i seem to remember that dns has generally been reliable (until recently, i guess) Probably because people used to use long TTLs (1 hour, 4 hours, whatever) and now the default behavior in services like Amazon Route 53 is to use 5 minutes.

Try Akamai managed CDN content. 20 seconds !!

Say I want to implement my own dynamic DNS solution on a VPS somewhere - if I set short TTLs am I causing problems for someone? How short is too short?

Re: DDoS Attack Against Dyn Managed DNS

#647
post #255
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…

OpenDNS does this: https://support.opendns.com/hc/en-us/articles/227987767-Dyna... It's called SmartCache.

I do this, too.

It's called HOSTS and djb's cdb constant database.

And one does not need to use a recursive cache to get the IP addresses. Fetching them non-recursively and dumping them to a HOSTS and a cdb file can sometimes be faster; I have a script that does that. Fetching them from scans.io can be even faster.

   cd||exit
   [ -c null ]||mknod null c 2 2 
   
   case $# in
   0)
   {
    sed '
         /#/d;
         /^[0-9]/!d;
    ' /etc/hosts \
     |{ 
        while read a b c d;
        do 
        echo +${#b},${#a}:$b-\>$a;
        done;
      }
    echo;
   } \
    |exec awk '!($0 in a){a[$0];print}' \
    |exec cdbmake $0.cdb $0.t||exit
   exec cdbdump null;
   exec cdbget $1 
First usage compiles and dumps database to screen. Second usage checks for presence of domainname and exits 0 if present otherwise exits 100. Third usage is if $0 is only two characters it will check for presence of domainname and if present print the IP and domainname in HOSTS format.

http://cr.yp.to/cdb.html

With all due respect to the enormous reliance on it that has built up over the past decades, DNS is not the internet. It is just a service heavily used for things like email and web. This does not mean, in an emergency, email and web cannot work without DNS. They once did and they still can.

The internet runs just fine without DNS. Some software may refuse to honour HOSTS and rely on solely on DNS. But that is a vulnerability of the software, not the internet. (And in such cases, e.g., qmail, I just serve my own zone via tinydns, which again is just a mirror of HOSTS.)

Re: DDoS Attack Against Dyn Managed DNS

#648
post #631

Earlier quoted context omitted.

Do you have a link on the opendns web site that refers to those specific Ips?

One can go even further and install DNSCrypt: https://dnscrypt.org/

Any downsides to using this? I'm tempted to start using it, but I'm not really sure if there's any particular thing I should consider first.

Re: DDoS Attack Against Dyn Managed DNS

#649

Earlier quoted context omitted.

That is not an appropriate tone for someone representing OpenDNS to take.

Why not? It's blunt, but to the point, honest, and passionate. Who cares about tone?

Because it's dismissive.

Re: DDoS Attack Against Dyn Managed DNS

#650
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 think a problem that you might be overlooking is that DNS lookups aren't just failing, they are also very slow when a DDOS attack is underway on the authority servers. This introduces a latency shock to the system which causes cascading failures.
Post reply on HN