AI-generated Key Takeaways
-
The Beta DoH service on dns.google.com using non-anycast IP addresses is deprecated and will be turned down.
-
The experimental version of the RFC 8484 API is deprecated, with dns.google/experimental redirecting to dns.google/dns-query.
-
Google Public DNS supports the JSON API at /resolve and plans to continue support until a comparable webapp-friendly DoH standard exists.
-
DoH applications should use dns.google instead of dns.google.com for Google DoH, regardless of the API used.
-
DoH clients should follow HTTP redirects, and applications need to be updated to ensure compatibility with these changes.
As part of the launch of DoH on the dns.google domain and the well-known anycast IP addresses for Google Public DNS, the Beta DoH service on the dns.google.com domain using other IP addresses is now deprecated and will be turned down.
The experimental version of the RFC 8484 API is also deprecated; dns.google/experimental is not supported, and dns.google.com/experimental will be migrated to dns.google/dns-query.
Timeline
Date | Turndown step |
---|---|
dns.google.com/experimental redirects to
dns.google/dns-query – DONE |
|
dns.google.com resolves to Google Public DNS
anycast IP addresses – DONE |
|
2019-09-24 | Old IP addresses for dns.google.com redirect to
dns.google – DONE |
2020-06-23 | dns.google.com redirects to dns.google everywhere |
Changes to this timeline are updated here and posted to public-dns-announce. Subscribe to that low-volume mailing list for updates.
- Thursday, August 1, 2019
Requests for
https://dns.google.com/experimental
get HTTP 301 redirects tohttps://dns.google/dns-query
.DoH applications using the JSON API at
/resolve
are not affected.To work with Google DoH, applications that used
/experimental
must support at least one of the following: