News for hackers. Stuff that matters.
Re:Possible Vendetta Behind the East Coast Web Slowdown by trendia on Friday October 21, 2016 @03:32PM (#12763835)
If you are unable to connect because of DNS problems, switch your DNS server to 8.8.8.8 (Google).

Edit: sorry there, this worked for me but apparently it's not guaranteed.

Re:Possible Vendetta Behind the East Coast Web Slowdown by lell on Friday October 21, 2016 @03:36PM (#12763877)
Didn't help me, heroku is still unreachable with DNS servers changed to 8.8.8.8 and 8.8.4.4.
Re:Possible Vendetta Behind the East Coast Web Slowdown by rashkov on Friday October 21, 2016 @03:45PM (#12763963)
Having good luck with opendns 208.67.222.222

They have other IPs as well, but that's what I'm using

Re:Possible Vendetta Behind the East Coast Web Slowdown by losvedir on Friday October 21, 2016 @05:07PM (#12764822)
I switched temporarily from those to Open DNS's 208.67.222.222 and things are working for now.

But, just to be clear, it's not Google's fault: 8.8.8.8 are not the authoritative name servers for the sites that are down. Rather, Dyn, the provider of the NS is down, and I presume Google (8.8.8.8) is correctly not returning any IP address because the underlying authoritative name server is not.

Presumably Open DNS is working because it's not abiding by the TTL it's supposed to? It's caching the underlying authoritative name server longer than it was told?

Re:Possible Vendetta Behind the East Coast Web Slowdown by detaro on Friday October 21, 2016 @05:11PM (#12764856)
Re:Possible Vendetta Behind the East Coast Web Slowdown by LeoPanthera on Friday October 21, 2016 @03:56PM (#12764053)
That didn't help me this morning. Switching to OpenDNS worked for Github but not for Twitter.
Re:Possible Vendetta Behind the East Coast Web Slowdown by esharte on Friday October 21, 2016 @03:48PM (#12763992)
I had to move my DNS servers off google today to get twitter to load.
Re:Possible Vendetta Behind the East Coast Web Slowdown by cafard on Friday October 21, 2016 @03:41PM (#12763918)
That would resolve neither python.org nor cpan.org this morning.