Servage Magazine

Information about YOUR hosting company – where we give you a clear picture of what we think and do!

Google’s public DNS service becomes safer

Saturday, July 27th, 2019 by Helge

Google_Public_DNS2Google announced  that their public Domain Name System (DNS) service will now be fully supported by the DNS-over-TLS security protocol, a technology that encloses DNS requests and lookups with the TLS (Transport Layer Security) protocol.

Google Public DNS was launched for the first time on December 3, 2009 and quickly became the world’s most widely used DNS resolver with 400 billion lookups per day and more than half of them are site sensitive. DNS resolvers are simply explained a feature that works “under the hood” to convert domain names to their corresponding IP addresses – which browsers use to connect to a specific web site web server.

DNS-over-TLS is used to protect DNS resolvers and those using DNS resolvers against so-called man-in-the-middle attacks that attackers can use to intercept Internet connections or to manipulate DNS data. The DNS-over-TLS protocol specifies a standardized way to provide security and privacy for DNS user-resolver traffic. In other words, Google’s change means that users can now secure their connections to Google Public DNS using TLS, the same technology that protects common HTTPS web connections.

Google is the world’s fifth online player to add DNS-over-TLS support to its public DNS resolver service. Cloudflare, CleanBrowsing, Quadrant Information Security and Quad9 have done so before. The search giant has implemented the DNS-over-TLS specification using the IETF’s recommendations RFC 7766 to minimize the challenges of using TLS (among other things, encryption can, as we know, lead to some performance loss). Read more about this topic on the official Google blog

Google's public DNS service becomes safer , 4.8 out of 5 based on 5 ratings
Categories: Guides & Tutorials
You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

No comments yet (leave a comment)

You are welcome to initiate a conversation about this blog entry.

Leave a comment

You must be logged in to post a comment.