I thought DNS (particularly public) was basically immune to DDoS?
If one DNS server is down, use the cached result or another server.
DNS is some of the most distributable, cachable data I can imagine.
Massive Dyn DNS outage
191–200 of 302 posts
Re: Massive Dyn DNS outage
#192Reddit is out -- my productivity is up, and I'm not happy about it.
Reddit is up for me, but Github is down. Goodbye productivity.
Re: Massive Dyn DNS outage
#193Pagerduty down, which is not very helpful.
Re: Massive Dyn DNS outage
#194Anyone with issues on AWS in North Virginia?
We've seen zero problems (standard stuff: EC2, S3, RDS, Redshift). I expected that with 1/3 of the internet down something would be broken.
Re: Massive Dyn DNS outage
#195Rollbar!!!! noooooo!!!!!
Re: Massive Dyn DNS outage
#196Ticketfly.com. Damn I really wanted to buy die Antwoord tickets
Re: Massive Dyn DNS outage
#197Earlier quoted context omitted.
Can we add a line to our /etc/hosts file with a hard-coded DNS entry to fix it in the meantime? What's the IP address?
I looked up an ip for twitter (via a google search) and still timeout on pings. [edit: twitter and github are both accessible again.]
For me it resolves to 192.30.253.113
Re: Massive Dyn DNS outage
#198add moz.com
Re: Massive Dyn DNS outage
#199I thought DNS (particularly public) was basically immune to DDoS? If one DNS server is down, use the cached result or another server. DNS is some of the most distributable, cachable data I can imagine.
> DNS is some of the most distributable, cachable data I can imagine.
Indeed. How can it be so broken? And, it seem that it would make sense to use the last known value if upstream is unavailable.
Re: Massive Dyn DNS outage
#200GitHub seems fine for me.