Michael S. Clark

Please share your test results. We’re curious. This is before we have our London location online (another week, approx), so the results will have some latency — but that’s only part of the DNS speed equation. And maybe you can run the tests again after London comes online. It should scream then… and if it doesn’t, we want to know.

John Roberts
OpenDNS
first name at opendns.com

Hi John, thanks for stopping by.
Are there any tests you want me to run in particular?

Don’t have anything formal yet.

Traceroute to the OpenDNS nameserver address (208.67.222.222) is one method, although the network latency that measures is only one of the two components.

Maybe use dig for the other part, to get a sense of the total response time, including network latency and the request processing (influenced by cache size, software speed, etc.).

We’ll have to get more specific in the future!

John

Since I’m running Windows, I had to download dig from here. I’ve made the required files available as a zip on this server too here. Remember, though to follow the instructions for installation, including putting the resolv.conf file in your system32 directory.

I ran dig against http://www.google.com and got the following result. For comparison, I also ran the same test using my ISP’s (PIPEX) DNS servers:

http://www.google.com” href=”http://www.ne0ge0.com/files/dig1.www.google.com.txt” rel=”nofollow”>dig1.www.google.com.txt
http://www.google.com” href=”http://www.ne0ge0.com/files/dig2.www.google.com.txt” rel=”nofollow”>dig2.www.google.com.txt

Anything else I can do to help you guys, just let me know.