DoQ (DNS-over-QUIC)
What is DoQ (DNS-over-QUIC)?
DoQ (DNS-over-QUIC), defined in RFC 9250, encrypts DNS queries using QUIC instead of TLS-over-TCP or HTTPS, avoiding the head-of-line blocking a single stalled connection can cause. AdminKit's DoH-vs-DoT guide compares DoQ's QUIC transport against those encrypted DNS alternatives and their privacy tradeoffs.
By AdminKit team, Netbase JSC · Updated
DoQ (DNS-over-QUIC), defined in RFC 9250, encrypts DNS queries and responses using QUIC instead of TLS-over-TCP (DoT) or HTTPS (DoH), while reusing the same UDP port 853 that DoT reserved, and negotiating itself over the connection’s TLS handshake via the doq ALPN identifier IANA registers. Because QUIC, defined in RFC 9000, builds the TLS 1.3 handshake into its own connection setup and carries each message on an independent stream, a single lost packet only stalls the query riding that one stream, rather than blocking every other in-flight query the way a single stalled TCP connection can under DoT. QUIC’s connection migration also lets an established DoQ session survive a client switching networks — moving from WiFi to mobile data — without restarting the handshake. DoQ is newer and less widely deployed than DoH or DoT: support exists in some recursive resolvers and client libraries, but it is still not a default option in mainstream operating systems or browsers the way DoH is. Unbound is one resolver with server-side support: its quic-port setting sets the port on which it provides DNS-over-QUIC service, and setting it to 0 disables QUIC. The privacy goal is identical to DoH and DoT — stopping an on-path observer from reading or tampering with DNS traffic — the difference is purely which transport carries the encrypted query.
AdminKit groups doQ (DNS-over-QUIC) under its DNS cluster — browse the AdminKit glossary index for other related terms.
Frequently asked questions
What transport does DoQ use that DoT and DoH don't?
QUIC -- DoQ encrypts DNS queries and responses over QUIC instead of TLS-over-TCP (DoT) or HTTPS (DoH), while reusing DoT's UDP port 853.
Why does a single lost packet matter less under DoQ than DoT?
Because QUIC carries each DNS message on an independent stream, so a single lost packet only stalls the query on that one stream, rather than blocking every other in-flight query the way a stalled TCP connection can under DoT.
What does QUIC's connection migration let a DoQ session do?
Survive a client switching networks -- moving from WiFi to mobile data -- without restarting the handshake.
Is DoQ as widely deployed as DoH or DoT?
No -- DoQ support exists in some recursive resolvers and client libraries, but it isn't yet a default option in mainstream operating systems or browsers the way DoH is.