Choose style:

Author Topic: Google Public DNS DNSSEC-validating resolution  (Read 437 times)

0 Members and 1 Guest are viewing this topic.

Offline perknh

  • Trusted User
  • Hero
  • *****
  • Posts: 3857
  • Karma: 303
  • Soy un huevo, nada más.
    • View Profile
  • Peppermint version(s): Peppermint 10
Google Public DNS DNSSEC-validating resolution
« on: November 15, 2017, 12:33:40 pm »
Google Public DNS DNSSEC-validating resolution over an encrypted HTTPS connection

Does Google Public DNS secure the so-called "last-hop" by encrypting communication with clients?

Yes! Traditional DNS traffic is transported over UDP or TCP without encryption. We also provide DNS-over-HTTPS which encrypts the traffic between clients and Google Public DNS. You may try it at:


DNS-over-HTTPS appears to me to be a new feature added to Google's Public DNS.  Is this Google's alternative to Cisco's DNSCrypt?  Also, why does my DNSCrypt still work when running Google's DNS if it is allegedly incompatible with DNSCrypt? :o

Here are the servers that are currently compatible with DNSCrypt.  Google Public DNS is conspicuously absent from this list.

By the way, these are NOT support questions.  Everything is working fine for me with Peppermint 8.  I'm only trying to increase my understanding of DNS by asking these two questions, BUT I am puzzled by this relatively new development within Google's Public DNS and why my I am still able to pass GRL Gibson's DNS Spoofability Test when running Google Public DNS with DNSCrypt.  :-\

Thank you,


We're all Peppermint users and that's what matters  ;).  -- AndyInMokum