is quic protocol down ?
last time quic working fine even not working at ipv4 , but now seem in both ipv4 and ipv6 down can't connect at all
I can confirm this issue. DNS-over-QUIC is not working on the latest stable version of AdGuard Home (v0.107.7). I believe this is NOT an AdGuard Home problem. The @nextdns team needs to update their DNS-over-QUIC implementation, because DNS-over-QUIC protocol is now finalized.
The udp port must be 853.
Adguard Home (v0.107.7) change log:
"DNS-over-QUIC: RFC 9250
The long-awaited DNS-over-QUIC protocol has finally graduated from a draft to being a real standard, RFC 9250. In this release, we add support for the final version of the standard in a backwards-compatible way."
This problem is also mentioned on the Github support page of AdGuard Home:
Developers of AdGuard Home have responded:
" RFC-version of DoQ is not compatible with the old draft versions, hence the issue.
AdGuard Home has already switched to the RFC-version of DoQ.
AdGuard DNS supports both the old drafts and the RFC-version.
Unfortunately, this behavior is only normal for the server-side (AdGuard DNS) since it can distinguish the version the client wants to use. The client (AdGuard Home) just uses the RFC-version and if the server is not compatible it won't get through.
Probably, the only way is to fix this on the NextDNS side. The fix is rather trivial, though. I'd suggest NextDNS to use the same approach as we do to support the old clients: https://github.com/AdguardTeam/dnsproxy/commit/c3b50a44f5b41cc0f385a0402e5dc127f08b0d1d#diff-6f8ef90801bf531405c62f0548dd80dc2edec8e10f96b0cd50c34544a7ea9c53R154 "
So, the next logical step would be that NextDNS also updates their DoQ implementation to final (RFC) version.