I've noticed some weird and inconsistent issues as well, shortly after moving to OpenDNS, but it is probably just coincidence.
These probs can be pretty difficult to track down, and typically the only way to really tell where the problem lies is to perform a packet capture, and analyze the time difference between DNS queries and answers. You may also find that your HTTP sessions may be taking a long time either to negotiate a 3-way handshake, or even further along in the application stream. So the problem may not even be related to DNS... but some of the many services the site has embedded in it's pages. Culprits I've seen are google analytics and other various counter sites can slow down page loads, giving the impression that the requested page is slow, but in actuality only a small piece won't load, blocking the page from completing it's download. I would 1st, set your computers DNS entries manually to the OpenDNS servers. This cuts out any weird caching or resolution issues on your router. If that yields the same result... try using other public DNS servers, e.g. 4.2.2.1, 4.2.2.2, 4.2.2.3, 4.2.2.4. To test them before you add em, do the following: dig @4.2.2.1 www.google.com If you continue to have trouble, you could install your own cache-only DNS server locally on your machine, and set your DNS entry to your loopback of 127.0.0.1. Beyond this... you're left with either local network issues, e.g. router, wireless, etc... or even upstream ISP probs which are a little more challenging to troubleshoot. -- Gilbert Mendoza PGP: 0x7403B303 Email: gmendoza at gmail.com http://www.savvyadmin.com https://launchpad.net/~gmendoza https://wiki.ubuntu.com/GilbertMendoza
