EkkoG
commented
2 years ago 看了一下 overture 的 DNS 请求是由 https://github.com/miekg/dns 构建消息然后发出的，所以 overture 要加 DoQ 的话应该需要 miekg/dns 支持
根据 miekg 的说法，现在的实现不太容易实现
quic-go uses Streams which are not net.Conn`s, and we don't want to pull all of that in this library. Quic/http3 is slowly happening in Go's std lib, until that is done I don't see what can be done in this library.
If you want to play with it yourself, various things can be wrapped in dns.Conn and the server could check if the conn support quic or some such
Originally posted by @miekg in https://github.com/miekg/dns/issues/1370#issuecomment-1132647664
After looking over the code I can't really see a simple way to make protocols pluggable, they are too tied into a lot of things such as the
Readerinterface which hasReadTCP(),ReadUDP()etc and none of that is applicable to DoQ.The design is also around having one listener listening for one connection that delivers DNS messages where QUIC is conn listener -> stream listener -> streams. Sure, that could be solved with channels etc but then it's workarounds which makes the code clunky and slow.
I think a better approach is to make my own module that mimics
dns.Serveras much as possible.Thanks for the reviews and discussion!
Originally posted by @jelu in https://github.com/miekg/dns/issues/1377#issuecomment-1140881423
Surge 作者发现疑似 Adguard 的实现有问题 https://github.com/AdguardTeam/dnsproxy/issues/260
ZeroClover
DoQ (DNS-over-QUIC) RFC 已经定稿，希望得到支持。