dnsproxy add DoH3

As @ainar-g said,

AFAIK, the Go standard library currently doesn't support HTTP/3, and probably won't until it graduates the draft standard phase. Once it does, the Go standard library will probably get an implementation shortly.

but it seems that go team will not implement it very soon. ^1 ^2

And I noticed that the dnsproxy is using quic-go for QUIC, and quic-go has a HTTP/3 implementation, so why not support it now? We can switch to the Go standard library once it has a implementation.

@ameshkov

Mar 09 '22 05:03 hellodword

@ainar-g How do you think about this?

May 24 '22 14:05 hellodword

Generally, it's not bad, we'll consider the PR, thank you!

May 24 '22 14:05 ameshkov

We're currently very busy with a large number of tasks in our projects. While we're generally not against an HTTP/3 upstream and server support, I personally have some reservations regarding whether or not it should be a separate kinds of upstream. I think that net/http supports optional switch to HTTP/3 using ALPN, but I'm not sure.

May 24 '22 14:05 ainar-g

https://security.googleblog.com/2022/07/dns-over-http3-in-android.html

Good news I guess.

Jul 21 '22 04:07 hellodword

Any estimate when HTTP/3 upstream will be added? This month, this quarter, this year, next year? Fully understand your primary focus is on AdGuard Home right now, but would be so cool to use DNSproxy with all "next-gen" DNS-protocols.

PS. Just noticed DNSCrypt released HTTP/3 support a few days ago as a teaser... ;-)

Aug 07 '22 08:08 iJorgen

Added here: https://github.com/AdguardTeam/dnsproxy/commit/823fa92f99c4bf1093bc922d4f47ff2f94314781

After all, we decided not to make a separate Upstream for DOH3 and extend the existing one.

Sep 16 '22 15:09 ameshkov