Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

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.



Didn't help me, heroku is still unreachable with DNS servers changed to 8.8.8.8 and 8.8.4.4.


Having good luck with opendns 208.67.222.222

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


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?


Yes, the call it "SmartCache": https://www.opendns.com/about/press-releases/opendns-introdu...


That didn't help me this morning. Switching to OpenDNS worked for Github but not for Twitter.


I had to move my DNS servers off google today to get twitter to load.


That would resolve neither python.org nor cpan.org this morning.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: