Google Public DNS is a Domain Name System (DNS) service offered to Internet users worldwide by Google. It functions as a recursive name server.Google Public DNS was announced on December 3, 2009,[1] in an effort described as "making the web faster and more secure."[2] [3] As of 2018, it is the largest public DNS service in the world, handling over a trillion queries per day.[4] Google Public DNS is not related to Google Cloud DNS, which is a DNS hosting service.
The Google Public DNS service operates recursive name servers for public use at the four IP addresses listed below.[5] These addresses are mapped to the nearest operational server by anycast routing.[6]
| Filters domains | ||
|---|---|---|
| Passes ECS | ||
| Validates DNSSEC | ||
| Via DoH | https://dns.google/dns-query | |
| Via DoT | dns.google | |
| Via IPv4 | 8.8.8.8 8.8.4.4 | |
| Via IPv6 | 2001:4860:4860::8888 2001:4860:4860::8844 |
The service does not use conventional DNS name server software, such as BIND, instead relying on a custom-designed implementation, conforming to the DNS standards set forth by the IETF. It fully supports the DNSSEC protocol since 19 March 2013. Previously, Google Public DNS accepted and forwarded DNSSEC-formatted messages but did not perform validation.[7] [8]
Some DNS providers practice DNS hijacking while processing queries, redirecting web browsers to an advertisement site operated by the provider when a nonexistent domain name is queried. The Google service correctly replies with a non-existent domain (NXDOMAIN) response.[9]
The Google service also addresses DNS security. A common attack vector is to interfere with a DNS service to achieve redirection of web pages from legitimate to malicious servers. Google documents efforts to be resistant to DNS cache poisoning, including “Kaminsky Flaw” attacks as well as denial-of-service attacks.[10]
The Google Public DNS64 service operates recursive name servers for public use at the two IP addresses listed below for use with NAT64.[11]
| Filters domains | |
|---|---|
| Passes ECS | |
| Validates DNSSEC | |
| Via DoH | https://dns64.dns.google/dns-query |
| Via DoT | dns64.dns.google |
| Via IPv6 | 2001:4860:4860::64642001:4860:4860::64 |
Google stated that for the purposes of performance and security, the querying IP address will be deleted after 24–48 hours, but Internet service provider (ISP) and location information are stored permanently on their servers.[12] [13] [14]
In December 2009, Google Public DNS was launched with its announcement[15] on the Official Google Blog by product manager Prem Ramaswami, with an additional post on the Google Code blog.[16]
In January 2019, Google Public DNS adopted the DNS over TLS protocol.[17]
At the launch of Google Public DNS, it did not directly support DNSSEC. Although RRSIG records could be queried, the AD (Authenticated Data) flag was not set in the launch version, meaning the server was unable to validate signatures for all of the data. This was upgraded on 28 January 2013, when Google's DNS servers silently started providing DNSSEC validation information,[18] but only if the client explicitly set the DNSSEC OK (DO) flag on its query.[19] This service requiring a client-side flag was replaced on 6 May 2013 with full DNSSEC validation by default, meaning all queries will be validated unless clients explicitly opt-out.
Since June 2014, Google Public DNS automatically detects nameservers that support EDNS Client Subnet (ECS) options as defined in the IETF draft (by probing name servers at a low rate with ECS queries and caching the ECS capability), and will send queries with ECS options to such name servers automatically.[20]
In March 2014, use of Google Public DNS was blocked in Turkey after it was used to circumvent the blocking of Twitter, which took effect on 20 March 2014 under court order. The block was the result of earlier remarks by Prime Minister Tayyip Erdogan who vowed to "wipe out Twitter" following damaging allegations of corruption in his inner circle. The method became popular after it was determined that a simple domain name block was used to enforce the ban, which would easily be bypassed by using an alternate DNS resolver. Activists distributed information on how to use the service, and spray-painted the IP addresses used by the service as graffiti on buildings. Following the discovery of this method, Google Public DNS was blocked entirely.[21] [22] [23]