DNS acts like the phone book of the Internet. If you had to look up hundreds or thousands of phone numbers every day, you’d want a directory that was fast, secure and correct. That’s what Google Public DNS provides for tens of millions of people.
Google Public DNS has become particularly popular for our users internationally. Today, about 70 percent of its traffic comes from outside the U.S. We’ve maintained our strong presence in North America, South America and Europe, and beefed up our presence in Asia. We've also added entirely new access points to parts of the world where we previously didn't have Google Public DNS servers, including Australia, India, Japan and Nigeria.
Shortly after launch, we made a technical proposal for how public DNS services can work better with some kinds of important web hosts (known as content distribution networks, or CDNs) that have servers all of the world. We came up with a way to pass information to CDNs so they can send users to nearby servers. Our proposal, now called “edns-client-subnet,” continues to be discussed by members of the Internet Engineering Task Force. While we work with the IETF, other companies have started experimenting with implementing this proposal.
We’ve also taken steps to help support IPv6. On World IPv6 Day, we announced our IPv6 addresses: 2001:4860:4860::8888 and 2001:4860:4860::8844 to supplement our original addresses, 18.104.22.168 and 22.214.171.124.
Google Public DNS’s goal is simple: making the web—really, the whole Internet!—faster for our users. If you’d like to try it yourself, please see our page Using Google Public DNS. For more information, please see our Introduction to Google Public DNS and Frequently Asked Questions.
Posted by Jeremy K. Chen, Ph.D, software engineer, Google Public DNS