Self sign-up has been disabled due to increased spam activity. If you want to get access, please send an email to a project owner (preferred) or at gitlab(at)nic(dot)cz. We apologize for the inconvenience.
I believe our whole team agrees that the HTTP layer is more trouble than worth for DNS.
As for QUIC, I haven't thought through all details of that. Knot Resolver team certainly has no current plans to implement it. Perhaps for starters "we" should use some proxies to plain UDP or TCP and defer internal implementation(s) to later.
If I understand it correctly (there are many variables like TCP fast open, TLS session resumption, 0-RTT), QUIC will improve latency for the first reply on a given connection (by one RTT, whether TLS-resumed or not). That seems mainly advantageous towards authoritative servers, but those are not considered yet (in the RFC draft). Towards resolvers the connections tend to be longer and aggregate many queries, so there... perhaps for links with higher packet loss it will be better latency-wise due to head-of-line blocking.
Based on QUIC implementations, and Knot Resolver using C programming language, I would suggest to use picoquic from Private Octopus Inc. that has contributed to the Internet Draft above: https://github.com/private-octopus/picoquic
Well, main question is: Is there any other DNS software considering QUIC? It would be almost pointless to implement something which is not going to be supported elsewhere.
Yes. In the past year DoH seems to be stealing almost all attention/interest, despite having come later than DoT. I don't think it will be easy to propagate yet another protocol.
Has this feature been added to the roadmap or is it expected to be supported soon? While exploring DNS Cache/Resolver/Forwarder options, I discovered that https://technitium.com/dns/ also supports DoQ, DoH/3, and XoQ. I hope there will be some updates regarding the progress of this feature.
It feels difficult to promise big things in advance. I'd say that DoQ support most likely will get into Knot Resolver in 2024 or 2025, for server side and forwarding at least.