NEWS: Google Public DNS

What is Google Public DNS?

Google Public DNS is a free, global Domain Name System (DNS) resolution service, that you can use as an alternative to your current DNS provider.

To try it out:

  • Configure your network settings to use the IP addresses 8.8.8.8 and 8.8.4.4 as your DNS servers or * Read our configuration instructions.

If you decide to try Google Public DNS, your client programs will perform all DNS lookups using Google Public DNS. Why does DNS matter?

The DNS protocol is an important part of the web's infrastructure, serving as the Internet's phone book: every time you visit a website, your computer performs a DNS lookup. Complex pages often require multiple DNS lookups before they start loading, so your computer may be performing hundreds of lookups a day. Why should you try Google Public DNS?

By using Google Public DNS you can:

  • Speed up your browsing experience. * Improve your security. * Get the results you expect with absolutely no redirection.
Reply to
John Navas
Loading thread data ...

It's spyware. It ties your IP to every single site you visit. If you have gmail or blogger, it can link them to your name. This info can be sold by google to government agencies and others.

Yes, sure, easy to remember, but never use it as your standard DNS server unless you can't resist nudist camps, and other exhibitionist activities. DNS : 8.8.8.8 []'s

Reply to
Shadow

It's also a bit slower for me...35 mS versus 21 mS for my usual DNS server.

Reply to
Char Jackson

Try running DNSbench:

Note the difference between cached (where the DNS server has the domain name to lookup in its local cache), versus uncached (where the DNS server has to forward the lookup to another server for resolution.

What I get in Santa Cruz CA on an AT&T DSL line is:

  1. 94.157. 1 | Min | Avg | Max |Std.Dev|Reliab%| ----------------+-------+-------+-------+-------+-------+ - Cached Name | 0.009 | 0.010 | 0.013 | 0.001 | 100.0 | - Uncached Name | 0.013 | 0.084 | 0.820 | 0.153 | 100.0 | - DotCom Lookup | 0.014 | 0.233 | 0.889 | 0.318 | 100.0 | ----------------+-------+-------+-------+-------+-------+ dnsr2.sbcglobal.net DNS Anycast Address Pool2
  2. 8. 8. 8 | Min | Avg | Max |Std.Dev|Reliab%| ----------------+-------+-------+-------+-------+-------+ - Cached Name | 0.028 | 0.029 | 0.033 | 0.001 | 100.0 | - Uncached Name | 0.033 | 0.097 | 0.297 | 0.068 | 100.0 | - DotCom Lookup | 0.063 | 0.152 | 0.231 | 0.054 | 100.0 | ----------------+-------+-------+-------+-------+-------+ google-public-dns-a.google.com Level 3 Communications

The AT&T DNS servers respond in 10 msec if it's in their cache, but take 84 msec if it has to forward the lookup. If it has to do a full lookup from scratch, it's 233 msec.

The Google DNS servers respond in 29 msec if it's in their cache, but take 97 msec if it has to forward the lookup. If it has to do a full lookup from scratch, it's 152 msec.

So, Google is actually faster for FQDN lookups, slower for cached lookups, and about the same for uncached lookups.

Reply to
Jeff Liebermann

You could also try running namebench.

I found that both give googles DNS as being slower than OpenDNS and my ISP's DNS with 8.8.4.4 response times,over several runs, being erratic while 8.8.8.8 gave fairly consistent results.

Using GRC's Benchmark

192.168. 1. 1 | Min | Avg | Max |Std.Dev|Reliab%| ----------------+-------+-------+-------+-------+-------+ + Cached Name | 0.024 | 0.027 | 0.037 | 0.003 | 100.0 | + Uncached Name | 0.027 | 0.073 | 0.296 | 0.067 | 100.0 | + DotCom Lookup | 0.043 | 0.070 | 0.106 | 0.028 | 100.0 | 208. 67.222.222 | Min | Avg | Max |Std.Dev|Reliab%| ----------------+-------+-------+-------+-------+-------+ - Cached Name | 0.024 | 0.027 | 0.029 | 0.001 | 100.0 | - Uncached Name | 0.031 | 0.121 | 0.794 | 0.146 | 100.0 | - DotCom Lookup | 0.030 | 0.101 | 0.180 | 0.051 | 100.0 |
  1. 8. 8. 8 | Min | Avg | Max |Std.Dev|Reliab%| ----------------+-------+-------+-------+-------+-------+ - Cached Name | 0.035 | 0.049 | 0.217 | 0.037 | 100.0 | - Uncached Name | 0.057 | 0.172 | 0.421 | 0.104 | 100.0 | - DotCom Lookup | 0.058 | 0.145 | 0.281 | 0.061 | 100.0 | ----------------+-------+-------+-------+-------+-------+
  2. 8. 4. 4 | Min | Avg | Max |Std.Dev|Reliab%| ----------------+-------+-------+-------+-------+-------+ - Cached Name | 0.032 | 0.063 | 0.345 | 0.073 | 100.0 | - Uncached Name | 0.053 | 0.161 | 0.388 | 0.090 | 100.0 | - DotCom Lookup | 0.049 | 0.145 | 0.248 | 0.053 | 100.0 | ----------------+-------+-------+-------+-------+-------+
Reply to
Bob

DNS = use to translate Domain -name to IP like google.com=64.233.169.103 < this is his IP and many other stoff

-- Posted via : news.mccarragher.com We remove Bad spam/sex/ads/other

Reply to
floffy

On Thu, 31 Dec 2009 10:16:33 +0000, Bob wrote in :

I'm using ISC.org 'dig' for testing, and my experience thus far is that Google DNS is comparable in speed to the best other DNS servers on the Internet, faster than many ISPs, and has been dead reliable.

Reply to
John Navas

Try

formatting link
for something more scientific.

Reply to
DevilsPGD

The Shadow knows. I agree with him/her. Why reveal anymore to Google than you do now?

There is also opendns.

Reply to
miso

Cabling-Design.com Forums website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.