The early results give a qualified “yes”. This is nothing earth shattering, because the intelligent mind should know by now that Google would not bring something less than satisfactory to market.
Google might put a beta label on something, but in that case, what is in beta will be eminently usable, without any major flaws. The DNS service has no such label.
A mention on Download Squad this morning states that though the DNS service is good, it might only be slightly better, if you have a good to great ISP, or tremendously better, if you have an ISP that uses less than enough horsepower on the DNS server –
Google’s Public DNS has been up and running for a few days now, and the reviews and benchmarks are slowly starting to trickle in. Initial results seem to suggest that it works well, but may not be a blanket solution for all, or even many, Internet users.
It seems to depend wildly from ISP to ISP. If you’re fortunate enough to have an Internet provider like Verizon’s FiOS that runs a finely-tuned, well-oiled network, Google Public DNS is simply not for you. If you’re one of the (many) that has poorly-maintained DNS servers, the Google service might help considerably. But we’re skirting the real issue here: does Google’s Public DNS outperform the current ‘industry standard’ provisions from OpenDNS? Yes, it does. Just.
Either way, we’re talking about a few milliseconds — milliseconds that add up over days or weeks. It’s well known that fractions of a second can change the outcome of someone looking to buy from an e-commerce website. I don’t know about you, but I actually find myself drumming my fingers impatiently when a site takes more than a second or two to load — crazy, when you consider just how quickly things are actually happening, compared to the online world a decade ago.
Let’s not forget that Google just launched this service. OpenDNS have been around for years. Let’s also not forget that their services are functionally different — Google just want to speed up the ‘net, while OpenDNS is an enterprise offering that can provide adult-content filtering and more.
For me, I have decided to stay with OpenDNS, but I have those Google DNS octets committed to memory, just in case OpenDNS should ever fail to do the trick; I’ll simply slap them into my router in a heartbeat. For now, it is a great backstop.