Domain name resolution is how the DNS turns a name like example.com into an IP address. A recursive resolver asks a chain of servers in order — first the root (“who runs .com?”), then the .com registry (“who runs example.com?”), then the domain’s authoritative name servers (“what is the IP?”). Caching means most lookups finish in milliseconds.
You type a name and a page appears. In the gap — usually a few hundredths of a second — a small relay race plays out across the globe. Following it step by step is the clearest way to understand how DNS really works.
What is domain name resolution?
Resolution is the act of resolving a name to an address: converting the words you can remember into the numbers a network can route. Because the global map of names is far too large for any one server to hold, resolution works by delegation — each level of the DNS hierarchy hands the query down to the level that knows more.
The players in a lookup
Four kinds of participant cooperate on every fresh lookup:
- The stub resolver — built into your device; it kicks off the request.
- The recursive resolver — run by your ISP or a public service (e.g.
1.1.1.1,8.8.8.8); it does the legwork. - The root and TLD servers — they direct the resolver toward the right registry and domain.
- The authoritative name servers — they hold the domain’s real records and give the final answer.
Resolution, step by step
Here is the full journey for an uncached request to www.example.com:
- Check the caches. Your browser, then your operating system, then your recursive resolver each check whether they already know the answer. If any do, the lookup ends here.
- Ask the root. If not cached, the resolver asks a root server where to find the
.comzone. The root replies with the.comservers. - Ask the TLD servers. The resolver asks the
.comregistry’s servers who is authoritative forexample.com. They reply with the domain’s name servers. - Ask the authoritative servers. The resolver asks
example.com’s name servers for the record (e.g. the A record forwww). They return the IP address. - Return and connect. The resolver hands the IP back to your device, your browser opens a connection, and the page loads.
- Cache the result. Every layer stores the answer for its TTL, so the next visit skips most of these steps.
Recursive vs iterative
From your device’s point of view the query is recursive — you ask once and get a final answer. From the resolver’s point of view the queries to root, TLD and authoritative servers are iterative — each returns a referral to the next server rather than the final answer.
The crucial role of caching
If every lookup walked the full chain, DNS would be slow and the root servers would be overwhelmed. Caching prevents both. Each answer carries a TTL (time to live) that says how long it may be reused. Within that window, resolvers, operating systems and browsers serve the cached answer instantly — which is why the second visit to a site resolves far faster than the first, and why most queries never reach the root at all.
TTL is your change-speed dial
Lowering a record’s TTL before a planned change (say, moving hosts) makes the new value propagate faster afterward, because old answers expire sooner. Raise it again once the change has settled to cut lookups.
The journey, summarized
| Step | Question asked | Answered by |
|---|---|---|
| 1 | “Do I already know this?” | Browser / OS / resolver caches |
| 2 | “Where is .com?” | Root server |
| 3 | “Where is example.com?” | .com registry servers |
| 4 | “What is the IP of www?” | Domain’s authoritative name servers |
| 5 | (connect & cache) | Your browser + every cache layer |
Why this matters to you
Understanding resolution demystifies the everyday quirks of running a domain: why a new site can take time to appear (caches and TTLs), why “it works for me but not for you” happens during propagation, and why pointing your domain correctly at the right name servers is what actually makes it load. The relay race is invisible, but knowing its steps turns DNS troubleshooting from guesswork into logic.
★ Key takeaways
- Resolution turns a name into an IP by querying a chain: cache → root → TLD → authoritative.
- A recursive resolver does the legwork and returns the final answer.
- Caching and TTL mean most lookups finish in milliseconds and rarely reach the root.
- Knowing the steps makes domain setup and propagation delays far easier to reason about.
Frequently asked questions
What is domain name resolution?
Domain name resolution is the process of turning a domain name like example.com into the IP address a computer needs to connect to it. The DNS does this by querying a chain of name servers until it finds the answer.
How long does DNS resolution take?
Usually milliseconds. A fresh, uncached lookup that has to walk the full chain — root, TLD, authoritative server — might take a fraction of a second; a cached answer is near-instant. Caching means most lookups never travel the whole path.
What is a recursive resolver?
A recursive resolver is the name server that does the legwork for you. Your device asks it once; it then queries the root, the TLD servers and the domain’s authoritative servers in turn, assembles the answer, caches it, and returns the IP address.
What is the order of a DNS lookup?
Caches first (browser, operating system, resolver), then the root, then the TLD registry servers, then the domain’s authoritative name servers, which return the final IP address. Each step narrows the search.
What is TTL in DNS?
TTL (time to live) is how long a DNS answer may be cached before it must be looked up again. A record with a short TTL updates quickly across the internet; a long TTL is cached longer, reducing lookups but slowing the spread of changes.