QNAME minimization
What is QNAME minimization?
QNAME minimization, specified in RFC 7816 and its 2021 update RFC 9156, limits how much of a query name a recursive resolver reveals to each server it asks, instead of sending the full domain name to the root and TLD servers too. AdminKit's DNS privacy guide weighs this resolver-side technique alongside DoH and DoT.
By AdminKit team, Netbase JSC · Updated
QNAME minimization (RFC 7816, also tracked on its IETF Datatracker page, updated by RFC 9156) is a privacy technique for recursive DNS resolvers that limits how much of a query name (the QNAME) gets sent to each server consulted while resolving it. ICANN’s Office of the CTO describes it the same way: QNAME minimization “limits the amount of information disclosed in DNS queries by only sending the necessary parts of a domain name.” Without it, resolving www.example.com by asking the root server, then the .com server, then example.com’s nameserver, traditionally sent the full name www.example.com to all three, even though the root server only needed to know about .com. With QNAME minimization, each server in the chain is asked only the minimum label needed to get the next referral, so the root server sees just a query related to .com rather than the full name, reducing how much of a user’s browsing or lookup activity any single server along the path can observe. Resolver software exposes this as an ordinary setting: the Unbound resolver’s configuration reference documents a qname-minimisation option that sends upstream servers only the minimum required labels, as a best-effort approach that falls back to the full QNAME when an upstream server replies with certain error codes. It limits what each resolver along the path sees, not what’s visible in transit — DoH and DoT instead encrypt the query itself against on-path observers.
QNAME minimization is part of AdminKit’s DNS cluster; the full AdminKit glossary lists other related terms.
Frequently asked questions
What exactly does QNAME minimization hide, and from whom?
It limits how much of a query name (the QNAME) a recursive resolver sends to each server consulted while resolving it -- so, for example, the root server sees only a query related to .com rather than the full name www.example.com.
How did resolution work before QNAME minimization?
Resolving www.example.com by asking the root server, then the .com server, then example.com's nameserver traditionally sent the full name www.example.com to all three, even though the root server only ever needed to know about .com.
Does QNAME minimization encrypt DNS queries?
No -- it only limits what each server along the resolution path gets to see, unlike transport encryption techniques such as DoH or DoT, which hide the query from on-path observers instead.
What's the difference between RFC 7816 and RFC 9156?
RFC 9156 is the 2021 update to the original RFC 7816 specification of QNAME minimization, refining the technique rather than replacing its core approach.