← Back to Learning Hub

DNS • Intermediate • 6 min read

QNAME Minimization: How Resolvers Reduce What They Leak

How QNAME minimization makes a recursive resolver send only the label each nameserver needs, shrinking how much of your browsing the DNS path can see.

When you look up a name like www.shop.example.com, a recursive resolver does not learn the answer from a single server. It walks down the tree, asking the root, then the .com servers, then the servers for example.com, until it reaches the one that holds the record. For most of the internet's history the resolver sent the entire name you asked for to every server along that path, even though the root and the .com servers never needed to see more than the next label. QNAME minimization changes that behavior so a resolver sends only the smallest piece of the name each server actually needs. This guide explains the privacy problem it solves, exactly what the queries look like before and after, the standard that defines it, and how to check whether the resolver you use has it turned on.

The privacy problem with normal resolution

A recursive resolver that has nothing cached starts at the root. To find www.shop.example.com it needs a referral toward .com, then toward example.com, then toward shop.example.com, and finally the record itself. The key point is that each server above the authoritative one only has to see the next label down to hand back a correct referral. The root servers only need to know you are headed into .com. The .com servers only need to know you want example.com.

Classic resolvers ignored that and sent the full question, www.shop.example.com, to every server in the chain. The result is that the root operators and the .com registry operators, along with anyone able to observe that unencrypted traffic, could see the complete hostname you were resolving even though they played no part in answering for it. That is a steady leak of browsing detail to parties who have no need for it, and it accumulates across every lookup every device on a network makes.

What QNAME minimization changes

With QNAME minimization the resolver reveals one label at a time, asking each server only the question that server is responsible for. It also tends to use the NS query type for the intermediate steps rather than the original type, so the upstream servers learn even less about the final record you want. Only the authoritative server for example.com, which is going to answer the query anyway, ever sees the full name.

Server queriedClassic resolver sendsMinimizing resolver sends
Rootwww.shop.example.com (A)com (NS)
.com serverswww.shop.example.com (A)example.com (NS)
example.com serverswww.shop.example.com (A)shop.example.com (NS)
shop.example.com serverswww.shop.example.com (A)www.shop.example.com (A)

The full hostname is still resolved correctly and just as completely. The difference is purely how much of it each intermediate server gets to see. Minimization is a property of the resolver alone, so you gain it simply by using a resolver that implements it, with no change to any zone you publish.

From experiment to internet standard

QNAME minimization was first described in RFC 7816 in March 2016 as an Experimental specification. Operational experience led to RFC 9156, published in November 2021, which obsoletes 7816 and places the technique on the Standards Track. RFC 9156 tightens the practical details: it recommends a cap on how many labels a resolver adds per step and an overall limit on the extra queries a single resolution may generate, so a deeply nested or deliberately hostile name cannot push a resolver into an excessive number of lookups. As of November 2026 the major open resolvers and the common resolver software default to minimization, so for most users it is already on.

How to check whether your resolver minimizes

You do not have to read source code to find out. A public test zone returns a plain yes or no, and a packet capture confirms it directly if you run your own resolver.

  1. Run dig txt qnamemintest.internet.nl +short against the resolver you want to test. The answer text states whether QNAME minimization is enabled on the resolver that reached it.
  2. To test a specific resolver, point the query at it, for example dig txt qnamemintest.internet.nl @9.9.9.9 +short.
  3. If you operate the resolver, capture its outbound queries while it resolves a fresh deep name and confirm the early packets carry only single extra labels with the NS type rather than the full hostname.
  4. Remember you are testing whichever resolver actually serves you. On many networks that is a forwarder or your ISP's server, not the address you think you configured, so test from the machine whose behavior you care about.

Trade-offs, failures, and limits

Minimization is not free. Splitting one question into several means a cold lookup can take a few more round trips, though caching absorbs most of that after the first query into a zone. A small number of misconfigured authoritative servers historically answered incorrectly to the intermediate NS queries, returning an error for an empty non-terminal name that does in fact have records below it. RFC 9156 defines fallback behavior for exactly this case, so a modern resolver retries with the fuller name rather than failing outright, and the broken-server problem has largely faded as servers were fixed.

What it does not do

QNAME minimization hides the full name from the servers above your domain, but the authoritative server for your domain still sees the complete query, because it must to answer. It also does nothing to encrypt the traffic, so an observer on the network path can still read the labels that do go out. For confidentiality against the local network and your resolver operator you need encrypted transport, which is why minimization pairs naturally with DNS over HTTPS and DNS over TLS. Understanding the walk down the tree also helps here; our explainer on recursive and authoritative DNS servers covers the roles each server in that chain plays.

Frequently asked questions

Does QNAME minimization require any change to my DNS records?

No. It is entirely a resolver behavior. If your authoritative servers answer standard queries correctly, including referrals for intermediate names, your zone already works with minimizing resolvers and there is nothing for you to configure.

Will minimization slow down my lookups?

Slightly, on the first query into a new zone, because the work is split across more steps. Once the intermediate referrals are cached the extra cost disappears for subsequent names in that zone, so the real-world impact on browsing is minimal.

Does it hide my browsing from my own resolver?

No. Your recursive resolver still sees every name you ask it to resolve, since it is the one doing the work. Minimization limits what the servers above your domain learn, not what your own resolver learns.

How can I tell if the resolver I use supports it?

Query the test zone qnamemintest.internet.nl for its TXT record. The response states plainly whether minimization is enabled on the resolver that handled your query, which is the simplest check available.

Is QNAME minimization a replacement for encrypted DNS?

No, they address different leaks. Minimization reduces what upstream authoritative servers see, while encrypted DNS hides your queries from observers on the network path and from eavesdroppers between you and your resolver. Use both together for the fullest coverage.

QNAME minimization is one of the quieter privacy wins in DNS: it costs you nothing to adopt and cuts off a decades-old leak to servers that never needed your full hostname. To see how your names resolve across regions and confirm the chain behaves as expected, run a query through the Valla DNS lookup tool.

Troubleshooting box

If results look inconsistent, compare authoritative nameservers first, then recursive resolvers by region. Capture snapshots every 10 minutes for deterministic incident timelines.

Try VallaDNS free →

Intermediate • 6 min

How to Find a DNS Record's TTL (Current Value)

Find the TTL currently set on a DNS record: read the TTL column in dig and nslookup, tell the authoritative TTL from a resolver's countdown, and confirm a change.

Intermediate • 7 min

How to Check If Nameservers Have Propagated

Nameserver changes live at the parent TLD and follow the registry NS TTL, not your zone. Check the parent delegation and confirm the new NS set worldwide.