DNS over QUIC (DoQ)

E40276

DNS transport protocol encrypted transport protocol network protocol

DNS over QUIC (DoQ) is a modern DNS transport protocol that uses the QUIC encrypted, multiplexed UDP-based transport to provide faster, more secure, and more reliable DNS queries than traditional methods.

Try in SPARQL Jump to: Surface forms Disambiguation Statements Elicitation Referenced by

AI illustration

All labels observed (3)

Label	Occurrences
DNS over QUIC	5
DNS over Dedicated QUIC Connections	1
DNS over QUIC (DoQ) canonical	1

How this entity was disambiguated

This entity first appeared as the object of triple T311026 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.

NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07

Target entity: DNS over QUIC (DoQ)
Context triple: [QUIC, transportFor, DNS over QUIC (DoQ)]

A. QUIC
QUIC is a modern, multiplexed transport protocol developed by Google and standardized by the IETF that runs over UDP to provide faster, more secure, and reliable web connections than traditional TCP-based HTTPS.
B. HTTP/3
HTTP/3 is the third major version of the Hypertext Transfer Protocol, built on the QUIC transport protocol to provide faster, more reliable, and secure web communication.
C. IETF QUIC Working Group
The IETF QUIC Working Group is a standards body within the Internet Engineering Task Force responsible for developing and maintaining the QUIC transport protocol and related technologies used by modern web protocols like HTTP/3.
D. HTTP/2
HTTP/2 is a major revision of the Hypertext Transfer Protocol that introduced features like multiplexing, header compression, and server push to significantly improve web performance over HTTP/1.1.
E. BCP 14
BCP 14 is an IETF Best Current Practice document that standardizes the use of requirement-level keywords like “MUST,” “SHOULD,” and “MAY” in technical specifications.
F. None of above. chosen
G. Unsure - the case is ambiguous/there is not enough information to decide.

NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07

Target entity: DNS over QUIC (DoQ)
Target entity description: DNS over QUIC (DoQ) is a modern DNS transport protocol that uses the QUIC encrypted, multiplexed UDP-based transport to provide faster, more secure, and more reliable DNS queries than traditional methods.

A. QUIC
QUIC is a modern, multiplexed transport protocol developed by Google and standardized by the IETF that runs over UDP to provide faster, more secure, and reliable web connections than traditional TCP-based HTTPS.
B. HTTP/3
HTTP/3 is the third major version of the Hypertext Transfer Protocol, built on the QUIC transport protocol to provide faster, more reliable, and secure web communication.
C. IETF QUIC Working Group
The IETF QUIC Working Group is a standards body within the Internet Engineering Task Force responsible for developing and maintaining the QUIC transport protocol and related technologies used by modern web protocols like HTTP/3.
D. HTTP/2
HTTP/2 is a major revision of the Hypertext Transfer Protocol that introduced features like multiplexing, header compression, and server push to significantly improve web performance over HTTP/1.1.
E. BCP 14
BCP 14 is an IETF Best Current Practice document that standardizes the use of requirement-level keywords like “MUST,” “SHOULD,” and “MAY” in technical specifications.
F. None of above. chosen

Statements (50)

Predicate	Object
instanceOf	DNS transport protocol ⓘ encrypted transport protocol ⓘ network protocol ⓘ
abbreviation	DoQ ⓘ
avoids	TCP head-of-line blocking ⓘ cleartext DNS on the wire ⓘ
canBeUsedBy	authoritative DNS servers ⓘ recursive resolvers ⓘ stub resolvers ⓘ
connectionEstablishment	client-initiated QUIC connection to DNS server ⓘ
defaultPort	853 ⓘ
definedInRFC	RFC 9250 ⓘ
designGoal	minimal changes to DNS message format ⓘ
feature	0-RTT resumption ⓘ connection-oriented communication ⓘ encryption ⓘ forward secrecy ⓘ head-of-line blocking avoidance ⓘ improved reliability ⓘ integrity protection ⓘ multiplexing ⓘ privacy protection against passive observers ⓘ reduced latency ⓘ
goal	improve DNS performance ⓘ improve DNS privacy ⓘ improve DNS reliability ⓘ
improvesOver	DNS over DTLS ⓘ DNS over TCP ⓘ DNS over UDP ⓘ
layer	application layer ⓘ
messageFormat	standard DNS wire format in QUIC streams ⓘ
providesFunction	transport for DNS messages ⓘ
publicationYear	2022 ⓘ
relatedTo	DNS over DTLS ⓘ linked to: DTLS DNS over HTTPS ⓘ DNS over TLS ⓘ
runsOver	QUIC connections on UDP port 853 ⓘ
securityModelSimilarTo	DNS over TLS ⓘ
standardizedBy	IETF ⓘ linked to: Internet Engineering Task Force
status	Proposed Standard ⓘ
supports	DNS queries ⓘ DNS responses ⓘ connection reuse for multiple DNS queries ⓘ multiple DNS streams over a single QUIC connection ⓘ server push is not used for DNS data ⓘ
uses	TLS 1.3 handshake within QUIC ⓘ
usesTransportProtocol	QUIC ⓘ
usesUnderlyingProtocol	UDP ⓘ
workingGroup	IETF DNSOP ⓘ IETF QUIC ⓘ linked to: IETF QUIC Working Group

How these facts were elicited