AdguardTeam
Add a low-level setting that enables DoH3 negotation for all DoH upstreams
Currently AdGuard will use DoH2 exclusively for all DoH upstreams that use https:// URLs.
We should add a low-level setting that enables both DoH3 and DoH2 (it's available as a flag in DnsLibs).
When this flag is enabled, DnsLibs tries to connect using both DoH3 and DoH2 simultaneously and chooses the one that was established faster, and then closes the slower one.
This setting should be disabled by default.
I agree with this issue, here is what I get when I try to use the h3:// domain with the most recent (4.5.0) version update for AdGuard and the Adguard-pro apps too.
@FsAguard62 several options:
- DoH3 does not work at all (maybe QUIC is blocked?)
- You're using native implementation
Well, I have figured out with the help from Vladislav on the Adguard chat today it was the Adguard VPN stopping the connection, and you can't use the “h3://” domain in the AGVPN standalone service I get the same error in there too!
I think it would be so much easier to have the selection of the service on the AdGuard (products) setting