Google Public DNS
Google Public DNS is a freely provided DNS (Domain Name System) service announced on 3 December 2009,[1] as part of Google's self-proclaimed effort to make the web faster.[2][3] Google Public DNS provides the following recursive nameserver addresses for public use,[4] mapped to the nearest operational server location by anycast routing:[5]
- IPv4 addresses
- 8.8.8.8
- 8.8.4.4
- 2001:4860:4860::8888
- 2001:4860:4860::8844
Contents |
[edit] Services
The service is still experimental. It does not use third party DNS management software such as BIND, instead relying on a custom-built implementation, with limited IPv6 support, conforming to the DNS standards set forth by the IETF. It also only partially supports the DNSSEC protocol.[7]
Some popular DNS providers practice a form of DNS hijacking while processing queries[dubious ]*, causing web browsers to redirect to an advertisement site run by the provider when a nonexistant domain name is entered, explicity breaking the DNS specification. In contrast, Google's service correctly replies with an NXDOMAIN code in this situation, and as a result, many users are now using the service for this reason alone[citation needed].
[edit] Privacy
It is stated that for the purposes of performance and security, only the user's IP address (deleted after 24 to 48 hours), ISP, and location information (kept permanently) are stored on the servers.[8][9][10]
Full list of items that are included in Google's permanent logs:
- Request domain name, e.g. www.google.com
- Request type, e.g. A (which stands for IPv4 record), AAAA (IPv6 record), NS, MX, TXT, etc.
- Transport protocol on which the request arrived, i.e. TCP or UDP
- Client's AS (autonomous system or ISP), e.g. AS15169
- User's geolocation information: i.e. geocode, region ID, city ID, and metro code
- Response code sent, e.g. SUCCESS, SERVFAIL, NXDOMAIN, etc.
- Whether the request hit our frontend cache
- Whether the request hit a cache elsewhere in the system (but not in the frontend)
- Absolute arrival time in seconds
- Total time taken to process the request end-to-end, in seconds
- Name of the Google machine that processed this request, e.g. machine101
- Google target IP to which this request was addressed, e.g. one of our anycast IP addresses (no relation to the user's IP)
[edit] History
- In December 2009, Google Public DNS was launched with its announcement[11] on the Official Google Blog by product manager Prem Ramaswami, with an additional post on the Google Code blog.[12]
[edit] See also
[edit] References
- ^ Geez, Google Wants to Take Over DNS, Too Wired, 3 December 2009
- ^ Introducing Google Public DNS, Official Google Blog
- ^ Pondering Google’s Move Into the D.N.S. Business New York Times, 4 December 2009
- ^ Google DNS Speed
- ^ Google DNS FAQ Countries
- ^ Announcement on public-dns-announce
- ^ "Frequently Asked Questions". http://code.google.com/intl/en-EN/speed/public-dns/faq.html. Retrieved December 4, 2009.
- ^ Public DNS Privacy FAQ
- ^ Google Privacy Policy
- ^ Google Public DNS and your privacy PC World, 4 December 2009
- ^ Introducing Google Public DNS Official Google Blog, 3 December 2009
- ^ Introducing Google Public DNS Google Code Blog, 3 December 2009
[edit] External links
|
|||||||||||||||||||||||||||||||||||
