Beware, whom you trust your DNS to. I have particularly enjoyed using OpenDNS, mainly because I travel a lot, and encounter a lot of broken DNS configurations. However, when OpenDNS goes wonky, it makes you really wonder if running local DNS makes more sense.
[-(byte@hermione)-(pts/1)-(11:57pm:27/02/2008)-]
[-(~)> ping www.google.com
PING google.navigation.opendns.com (208.67.219.231) 56(84) bytes of data.
--- google.navigation.opendns.com ping statistics ---
7 packets transmitted, 0 received, 100% packet loss, time 6000ms
Clearly, not good? Quick edit of /etc/resolv.conf, and I’m quite happy to use local DNS. Oops, it seems like OpenDNS is clearly down now (can’t even reach opendns.com). Ironically, only from my Unwired Internet account.
The difference in traceroute output (for status.opendns.com):
12 38.104.140.46 (38.104.140.46) 261.618 ms 267.483 ms 268.207 ms
13 208.67.219.60 (208.67.219.60) 220.762 ms 220.735 ms 220.709 ms
From hop 12, to hop 13, it is unreachable. Let’s hope this temporary problem, disappears.
Update: Its back online, 1.45am.
Technorati Tags: opendns, google, resolv.conf, unwired