Google Launches Public DNS Service

Google has just launched its very own public Domain Name System resolver, with which the company hopes to speed up internet traffic. The search giant claims its DNS is more secure (through protection against cache poisoning attacks) and faster than others.

I’m sure most of you are aware of what the Domain Name System does. When you type in a web address, you expect to be taken to said web address. DNS takes care of that for you by converting the address you typed in into its numerical variant, the IP address, making sure you actually get to the page you typed in.

Google claims that its DNS service is faster than others. “In addition to load-balancing user traffic to ensure shared caching, Google Public DNS implements ‘smart’ caching to increase the speed of responses,” the company states, “Google Public DNS independently resolves domain names and keeps the resolutions in the cache until their time-to-live expires, at which point they are automatically refreshed. The cycle of caching and refreshing is performed offline, asynchronously with user requests, so that responses are almost always available directly from cache.”

When it comes to security, Google is trying hard to prevent cache poison attacks. “Google has implemented several recommended solutions to help guarantee the authenticity of the responses it receives from other nameservers, and to ensure our servers are not used for launching DoS attacks,” Google explains, “These include adding entropy to requests, rate-limiting client traffic, and more.”

“The average Internet user ends up performing hundreds of DNS lookups each day, and some complex pages require multiple DNS lookups before they start loading. This can slow down the browsing experience,” explains Prem Ramaswami, product manager at Google, “Our research has shown that speed matters to Internet users, so over the past several months our engineers have been working to make improvements to our public DNS resolver to make users’ web-surfing experiences faster, safer and more reliable.”

Google has put together a document detailing the configuration instructions for Google Public DNS for Windows, Mac OS X, Linux, routers, and other devices. Google warns that playing with these settings is for advanced users only, so be warned.

An obvious concern here is privacy. There seems to be nothing but good news. Google explicitly states that “Google Public DNS never blocks, filters, or redirects users”. Good, but what about logging? The privacy policy for Google Public DNS is very reasonable, claims Lauren Weinstein, co-founder of PFIR (People For Internet Responsibility) and founder of the PRIVACY Forum.

“Google has obviously recognized the sensitivity of this issue,” Weinstein writes, “Their separate privacy policy for the Google Public DNS strikes me as utterly reasonable, particularly given its very rapid (24-48 hours) deletion of what I would consider to be the key privacy-sensitive data.”

If you’re adventurous, feel free to try it out.

61 Comments

  1. 2009-12-03 11:02 pm
    • 2009-12-04 12:58 am
      • 2009-12-04 1:06 am
        • 2009-12-04 1:16 am
        • 2009-12-04 3:04 pm
    • 2009-12-04 11:34 am
    • 2009-12-04 1:17 pm
      • 2009-12-04 1:50 pm
  2. 2009-12-03 11:05 pm
    • 2009-12-03 11:19 pm
      • 2009-12-03 11:30 pm
        • 2009-12-03 11:38 pm
      • 2009-12-04 3:23 am
        • 2009-12-04 4:03 am
          • 2009-12-04 7:16 am
          • 2009-12-04 3:42 pm
          • 2009-12-06 5:24 pm
      • 2009-12-04 3:44 am
        • 2009-12-04 8:34 pm
  3. 2009-12-03 11:15 pm
    • 2009-12-04 12:24 am
    • 2009-12-04 3:40 pm
      • 2009-12-04 7:19 pm
      • 2009-12-07 5:24 pm
  4. 2009-12-03 11:46 pm
    • 2009-12-03 11:55 pm
      • 2009-12-04 2:31 am
        • 2009-12-04 2:37 am
          • 2009-12-04 11:15 am
          • 2009-12-04 3:09 pm
  5. 2009-12-04 12:24 am
  6. 2009-12-04 12:30 am
    • 2009-12-04 12:55 am
      • 2009-12-04 3:54 am
    • 2009-12-04 12:17 pm
      • 2009-12-04 2:22 pm
  7. 2009-12-04 1:03 am
  8. 2009-12-04 1:21 am
  9. 2009-12-04 1:29 am
    • 2009-12-04 2:07 am
      • 2009-12-04 3:11 pm
  10. 2009-12-04 2:27 am
    • 2009-12-04 2:36 am
      • 2009-12-04 9:25 am
      • 2009-12-04 12:36 pm
    • 2009-12-04 10:02 am
    • 2009-12-04 12:06 pm
  11. 2009-12-04 2:58 am
    • 2009-12-04 3:03 am
      • 2009-12-04 10:04 am
        • 2009-12-04 12:37 pm
          • 2009-12-04 4:59 pm
  12. 2009-12-04 3:16 am
  13. 2009-12-04 4:35 am
    • 2009-12-04 6:01 am
  14. 2009-12-04 7:36 am
  15. 2009-12-04 12:35 pm
  16. 2009-12-04 2:06 pm
  17. 2009-12-04 2:49 pm
  18. 2009-12-04 3:08 pm
  19. 2009-12-05 6:21 pm