Google DNS Servers

Know About Google DNS Servers

Google Public DNS is a type of Domain Name System (DNS) service by Google for Internet users worldwide.  It functions like a recursive name server.
Know About Google DNS Servers
Google DNS

  Google Public DNS was announced on 3 December 2009, described as "making the web faster and more secure". As of 2014, it is the world's largest public DNS service, handling 400 billion requests per day. Google public DNS is not related to Google Cloud DNS, the DNS hosting service. 


  Service
  The Google public DNS service starts a recurring name server for public use after four IP addresses.  Addresses are mapped to the nearest operational server by any routing route.
  Ipv4 addresses8.8.8.8
  8.8.4.4
  Ipv6 addresses2001: 4860: 4860 :: 8888
  2001: 4860: 4860 :: 8844
  The service does not use DNS name server software, such as BIND, to conform to the DNS standards set by the IETF, rather than relying on custom-designed implementations. It supports the DNSSEC protocol since 19 March 2013. Previously, Google Public DNS had accepted and forwarded DNSSEC-formatted messages, but not verified.
Google DNS Servers
Google DNS Servers

  Some practice DNS hijacking while processing the DNS provider's query, redirecting web browsers to provider-run ad sites when none are queried without a domain name. This is considered intentional breaking of the DNS specification. The Google service provides the correct answer with a non-existent domain response.
  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 pages to malicious servers. Google documents try to be resistant to DNS cache poisoning, including "Cumminsky Flav" attacks, as well as service attacks. 


  Google claims various efficiency and speed benefits, such as using any reconquest routing to send user requests to the nearest data center, over-provisioning the server to handle denial-of-service attacks. And loading the server using two cache levels with a smaller per-host cache. Most popular names and another pool of servers containing partitions by name  Can be.  This reduces the second level of cache fragmentation and cache miss rate which can result in an increase in the number of servers.
  Secluded
  Google stated that for performance and security purposes, the query IP address will be deleted after 24–48 hours, but the Internet service provider and location information is stored permanently on their servers.
  According to Google's general privacy policy, "We [Google] may associate personal information from one service, including personal information, information from other Google services".  However, Google Public DNS's policy specifically states that "We do not correlate or combine information from our temporary or permanent logs with any personal information that you have provided to Google for other services."
  History
  In December 2009, Google Public DNS was launched by Product Manager Prem Ramaswamy with his announcement on the official Google Blog with an additional post on the Google Code blog.
  In January 2019, Google DNS adopted DNS over the TLS protocol.
  DNSSEC
  At the launch of Google Public DNS, it did not directly support DNSSEC.  Although RRSIG records can be verified, the AD (Authentic Data) flag was not set in the launch version, meaning the server was unable to validate the signature for all data.  This was upgraded on January 28, 2013, when Google's DNS servers began quietly providing DNSSEC validation information, but only if the client explicitly set the DNSSEC OK (DO) flag to its query.  This service, requiring a client-side flag, was replaced by default on 6 May 2013 with full DNSSEC validation, meaning that all queries will be validated until the client explicitly exits  .
  Customer subnet
  Since June 2014, Google Public DNS automatically detects names that support the EDET client subnet (ECS) options as defined in the IETF draft (by examining name servers at low rates with ECS queries  And caching ECS ​​capability), and will send queries with ECS options for such name servers automatically.
  Censorship in turkey

  In March 2014, the use of Google Public DNS was blocked in Turkey as it was used to prevent the blocking of Twitter, which took effect on 20 March 2014 under a court order.  The bloc was the result of earlier remarks by Prime Minister Tayyip Erdogan, who "wiped out Twitter" after damaging allegations of corruption within his inner circle.  This method became popular after determining that a simple domain name block was used to enforce the restriction, which would be easily bypassed using alternative DNS systems.  Workers distributed information about using the service, and spray-painted IP addresses used by the service as graffiti on buildings.  After discovering this method, the government moved to block Twitter's IP address directly, and Google public DNS was completely blocked.

Comments