Are those times from ping or from a timing command?
ping gives you the times between the sending and receiving of the ping ICMP packet. That is way after ping did a DNS resolve when you gave it a host-domain name instead of an IP address.
I would go with google or else run my own caching DNS server.
I currently use my ISP servers, which do not redirect on “not found” pages. If they start that redirecting ****, I will probably start running a caching server, though I might first try google.
About 2 years ago I did some testing (will try to find the page where a proper testing method was explained in just a few steps, to see what was best for me. Google and OpenDNS were at the same level, both much faster than my ISP. Since Google’s are so easy to remember, it’s become a sort of habit to use them.
Here’s the link. Change the DNS servers wherever you stored them, and compare the differences in output. I found that the dig output reports much shorter query times for OpenDNS and Google compared to my ISP. And, I feel the difference.
My ISP does not do these redirects, glad they don’t.
I’m sorry but ping is the wrong way to do this; it times the network connection between you and the server, and doesn’t tell how fast the DNS lookup process itself responds. (In a side note, in a galaxy far, far away - back when dial up was annoying, but not yet embarrassing - I used to have an ISP which had no clue how to run a network, and their DNS was almost hilariously bad. Ping did give some indication, but at some point, their DNS servers would effectively stop responding, but you could still just about get a ping packet to return. The name lookup part just adds another layer that can go wrong and which isn’t fully tested with just a ping.)
openDNS also does the ‘we didn’t find the page you actually wanted, so here’s something irrelevant’ thing, and some people might find that rules them out; I find that irritating, but not a total show stopper. OTOH, at least they are doing something with DNS security, which is something that needs taking seriously.
From what i remember, there don’t seem to be good DNS benchmarking apps (I think there is one, but I don’t remember the name, but it didn’t do as nice a job of presenting the results as DNSbench when I last looked, ~5 years ago) for Linux, but DNSbench works well in wine.
[QUOTE=]Try out namebench. It hunts down the fastest DNS servers available for your computer to use. namebench runs a fair and thorough benchmark using your web browser history, tcpdump output, or standardized datasets in order to provide an individualized recommendation. namebench is completely free and does not modify your system in any way. This project began as a 20% project at Google.
namebench runs on Mac OS X, Windows, and UNIX, and is available with a graphical user interface as well as a command-line interface.
[/QUOTE]