Google Public DNS Wants To Speed Up Your Browsing

Google today launched a new, free DNS service—called Google Public DNS—aimed at making your web browsing experience even faster. Here's how it works:

For those of you who are unfamiliar with DNS (and it's cool if you are—as long as DNS is working, most people never need to know what's going on), Google offers an explanation:

Most of us aren't familiar with DNS because it's often handled automatically by our Internet Service Provider (ISP), but it provides an essential function for the web. You could think of it as the switchboard of the Internet, converting easy-to-remember domain names - e.g., www.google.com - into the unique Internet Protocol (IP) numbers - e.g., 74.125.45.100 - that computers use to communicate with one another.

Google Public DNS, then, aims to replace your ISP's default DNS with a (hopefully) faster, safer, and more reliable alternative. Google Public DNS isn't the first freely available alternate DNS we've seen. OpenDNS is an excellent DNS alternative (it boasts keyboard shortcuts, parental filters, and more), but—for better or worse—we're guessing that even more people may be interested in Google's offering.

To set up your computer or router to use Google Public DNS, hit up Google's instructions (they've got specific instructions for Windows, Mac, Linux, or your router).

I swapped my DNS to Google's service earlier today and so far my page loading seems to have a spring in its step, but you know how these things go. If you give it a try, let's hear whether things are feeling snappier for you in the comments.

Google Public DNS [Google via Google Code Blog]


Comments

    That spring in your browsing step is probably a placebo, unless its seconds faster, you will hardly notice it, best to do some speed tests, would be good if Google had released them, but good on you Google for offering yet another fantastic service. I guess it would actually do speed up the Google factory (Google & its various apps.)

    This is all well and good. However it takes me 360ms to ping their DNS servers. So somehow i dont think it will be quicker than my local 24ms server.

    Sage: Which your local DNS server then has to go upstream anyway, so you are still a few hops away and possibly over 100ms before you get a lookup response.

    Some ISPs (I know iiNet for certain) determine their "free zones" via DNS - if you change your DNS server from your ISP's to OpenDNS, Google Public DNS or similar, stuff which is supposed to be quota-free starts becoming counted.

    -__- Wonderful, 8.8.8.8 & 8.8.4.4 are 120ms from Melbourne. ISP's DNS is 30ms.

    And again, another tech for the US... at least for now

Join the discussion!

Trending Stories Right Now