Pro&Con: Using Google's Public DNS as 'default' forwarders

Hello Experts,

in a recent answer here on EE an Expert said this: should be considered really more or less a kind of test DNS server.

I have to admit I never gave it much thought and implementing Google's Public DNS as a common practice since a few years, hence I replied: and point to the load balancers of Google's public DNS. Since these are in truth not a SOA for any domain (and never will be by design). I think of them as perfect forwarders since they will only forward themself. They are also pingable and - as most of the things operated by Google - near perfectly reliable. The DNS servers from my ISPs are not nearly as fast and available. See Google's statement

What are your thoughts?
LVL 13
Daniel HelgenbergerAsked:
Who is Participating?
kevinhsiehConnect With a Mentor Commented:
If you want to find DNS servers that are fast for you, check out Seve Gibson's free DNS Benchmark tool. Your ISPs servers might not be a good choice. I personally use the OpenDNS  servers because of the filtering they do.
wolfcamelConnect With a Mentor Commented:
personally I like to stick with the "nearest" DNS which would be the ISP, as this reduces the number of hops to do a lookup - and people like to see a webpage START loading quickly.

However, there is no guarantee that they are going to process the request any quicker. I have also had problems with an ISP caching an incorrect entry for far too long - but this could happen with anyone - at least with the ISP I can ring them and point out the issue - something I would expect very difficult with google.

As to security? Smaller target vs better security?
gurutcConnect With a Mentor Commented:
Also, google will track your requests.  That's a for-sure!

- gurutc
I must say - thanks kevinhsieh - that dns benchmark app is cool - I just ran it on a few of my clients servers to test dns performance and make sure they are using a fast forwarder - in Australia I found that Telstra seems to have the best performing DNS for non-cached requests - while the dns of the actual ISP wins for cached requests (as you should expect).
Daniel HelgenbergerAuthor Commented:
Thank you guys for your Input on that, esp. kevinhsieh for the benchmark-tool! Enabled me to find out my best performing DNS.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.