Google Public DNS now supports RFC 8484 DoH on

Skip to first unread message

Alexander Dupuy

Jun 26, 2019, 1:58:14 PM6/26/19

Dear Google Public DNS users,

In the Google Security Blog today, we are announcing GA support for for the RFC 8484 standard DNS over HTTPS (DoH) protocol web API. In addition to full support for the final RFC standard version, we now support the DoH API from and our other anycast IP addresses.

Technical details of the updated service are in our DoH documentation, and DoH application developers and users of those applications will need to migrate to the new DoH endpoints in the next few months.

If you have a problem using the updated Google DoH service, you can create an issue on our tracker or ask on our discussion group. As always, please provide as much information as possible to help us investigate the problem!

Alexander Dupuy

Alex Dupuy

Jul 12, 2019, 4:35:07 PM7/12/19
to public-dns-announce
A reminder for anyone using DNS over HTTP (DoH) with the URL.

In just over a week, starting on July 23, support for early IETF internet draft versions of DoH at will be discontinued, and DoH queries to the service will receive HTTP 301 redirects to (preserving any ?dns=... GET parameter).

Anyone using a DoH client that uses should reconfigure it to use the new URL, and in some cases may need to update the software of the DoH client. Clients that may be configured to use this deprecated URL include:
Older versions of the CoreDNS DoH client support are not compatible with the RFC 8484 DoH API (they use an obsolete MIME type). Developers using CoreDNS-based DoH clients should be sure to update to a more recent version of CoreDNS using the application/dns-message MIME type. This is necessary to work with the DoH service at

Developers should consider adding support for following HTTP redirects so that these sorts of changes are transparent to users. Anyone can test HTTP redirect support in a DoH client by configuring the DoH URL with an base. DoH queries to are already redirected in exactly the same way that queries to will be redirected starting July 23.

Reply all
Reply to author
0 new messages