Comment 14 for bug 220482

This is a problem with opendns.com. If I were you, I'd just ditch them.

If you want to spend the energy you can try to find out exactly where the problem is with them and try to get them to fix it. opendns.com is a solution only for websurfing and a bad one at that. Any other web activity will likely be flakey. Compare the output of these two commands and see for yourself "dig www.google.com @ns1.google.com" (the real deal) and "dig www.google.com @208.67.222.222" (the lie that opendns.com is telling you)

Closing as invalid, opendns.com is to blame.