Feature Request: Native DDR (RFC 9462) Support for NextDNS – Automatic DoH3 Upgrade on Android

Hi NextDNS team,

Following the recent discussion about enabling system-wide DNS-over-HTTPS on Android through its native Private DNS functionality, I’d like to request native support for Discovery of Designated Resolvers (DDR, RFC 9462) in NextDNS.

Android has built-in support for DDR-based resolver discovery, which can allow compatible devices to discover and upgrade to encrypted DNS transports, including DNS-over-HTTPS over HTTP/3 (DoH3), when the necessary platform features and resolver records are available.

Currently, NextDNS users may need workarounds involving custom domains or intermediary services to take advantage of this capability. Native DDR support could make the experience significantly simpler and more seamless.

Potential benefits include:

• Native Android integration: Enable compatible devices to discover NextDNS's supported encrypted DNS endpoints without requiring custom workarounds.
• Improved connectivity: DoH3 over HTTP/3 uses QUIC over UDP port 443, which may work on networks where DNS-over-TLS traffic on TCP port 853 is blocked, provided UDP traffic is allowed.
• Simpler configuration: Reduce the need for custom domains, Cloudflare Workers, or additional DNS proxy applications.
• Preserved NextDNS functionality: Ideally, users would retain their existing NextDNS profile, including blocklists, allowlists, parental controls, and analytics.

I understand that implementing DDR for a profile-based DNS service may introduce additional considerations, particularly around reliably associating discovered resolver endpoints with the correct NextDNS profile.

Is native DDR support on the NextDNS roadmap? If so, it would be great to learn whether there is an estimated timeline or any technical considerations the community could help address.

Thank you for your continued work on NextDNS and for considering this feature request.

Reference: https://www.reddit.com/r/nextdns/comments/1xe03ic/you_can_actually_do_systemwide_dnsoverhttps_with/