Hacker News Reader

Comment by epikur | Hacker News Reader

Chrome warns of an SSL error when I try to visit his site, and when I click proceed, I see an OpenDNS page about nameservers failing.

And yet, isup.me says it's up. Interesting.

It works fine here. Why use OpenDNS? They mess with your DNS results. Instead, try 8.8.8.8 or 8.8.4.4: http://code.google.com/speed/public-dns/docs/using.html

Google DNS makes for a suboptimal Netflix CDN load-balancing experience. :(

Would OpenDNS be any better in that regard?

That shouldn't be. 8.8.8.8 is anycast and so should be nearby.

It's down for me, here's a mirror:

I'm not having any problems myself, but here's the output from dig for it.

  louisck.net.            14400   IN      A       75.119.221.139

I got that for a while yesterday. The site probably changed nameservers and IPs, and your/your ISP's cache hasn't expired yet.