2

DNS-over-QUIC? (DoQ)

Apparently DNS-over-QUIC (DoQ) is an official standard now and AdGuard moves from DoH to DoQ:

https://adguard.com/en/blog/dns-over-quic-official-standard.html

What are NextDNS's plans regarding this?

(for example for the CLI and the iOS/macOS Apps)

17 replies

null
    • entrepreneur, academic educator
    • Erwin
    • 2 yrs ago
    • Reported - view

    they already support DoQ for a while

      • iOS Developer
      • Rob
      • 2 yrs ago
      • Reported - view

      Erwin Boermans I know they do, but I thought their Apps use DoH?

    • Patrik_Kro
    • 2 yrs ago
    • Reported - view

    NextDNS currently does not support the final version of DoQ standard. Because of this, there are compatibility problems between AdGuard apps and NextDNS DoQ.

    Read this:

    https://help.nextdns.io/t/83hddp1/is-quic-protocol-down

    https://github.com/AdguardTeam/AdGuardHome/issues/4644

      • Leonard
      • 2 yrs ago
      • Reported - view

      Patrik KroNextDNS had fixed this issue, now their DoQ can work in the AdGuard Home.

      • Aidan_Gee
      • 2 yrs ago
      • Reported - view

      Leonard it’s no longer working for iOS unfortunately :(

      • Pierre_Cartier
      • 2 yrs ago
      • Reported - view
    • Luke_Skywalker
    • 2 yrs ago
    • Reported - view

    Exciting times! Looking fwd to give it a go

    • Luke_Skywalker
    • 2 yrs ago
    • Reported - view

    Any timeline for the original question on this post?

                What are NextDNS's plans regarding this? 

                 (for example for the CLI and the iOS/macOS Apps)

    • NextDNs
    • 2 yrs ago
    • Reported - view

    Our apps will stay on DoH, leveraging Quic (DoH3) when available. DoH is more efficient when redundant metadata needs to be transported with the queries (client name etc).

    • Aidan_Gee
    • 2 yrs ago
    • Reported - view

    Official response by AdGuard here:

    "AdGuard DoQ protocols will be changed to the new version in the next update. The best solution right now is to force port 853 manually."

    • Amit_Saini
    • 2 yrs ago
    • Reported - view

    This works: quic://dns.nextdns.io:853

    This does not work: quic://personalpaiddns.dns.nextdns.io:853

    Is this something needs to be turned ON on the backend by the devs, to make it work with personal accounts for NextDNS? 

Content aside

  • 2 Likes
  • 2 yrs agoLast active
  • 17Replies
  • 4059Views
  • 9 Following