Step 1 · The pattern
Ask the resolver
A browser needs an IP address for a name, so it asks a recursive resolver. If the resolver already knows the answer, it replies from its cache in a millisecond.
- lookup
- answered
In short
Resolution chain: how it works and how it breaks
Before a browser can connect to a site it needs an IP address, and it gets one by asking a recursive resolver, usually run by an ISP or a public service. If the resolver has no cached answer it walks a chain. A root server says who handles .com. The .com servers say which name servers are authoritative for your domain. Those give the address. The resolver caches the result for the record's time-to-live, so most lookups never leave the cache. That makes your authoritative name servers a dependency of everything you run. If they are unreachable, nothing breaks at first, because resolvers still hold answers. Then TTLs expire around the world and the site disappears, with every server healthy. The delay makes the cause hard to see. List name servers from at least two independent providers.
How this comes up in interviews
"Walk me through what happens between typing a hostname and the browser having an IP address. Where can it fail?"
Then they ask
- Your only DNS provider goes down. When do users notice, and why not immediately?
- How would you remove your DNS provider as a single point of failure?
- Why is a DNS outage often blamed on an unrelated recent change?
A strong answer covers
- The browser asks a recursive resolver, which answers from cache or walks the chain on a miss.
- The root points to the TLD servers, the TLD points to your authoritative name servers, and they give the address.
- The resolver caches the answer for the record's time-to-live, so most lookups never leave the cache.
- If authoritative servers fail, nothing breaks at first. The site disappears gradually as TTLs expire.
- List name servers from at least two independent providers so a resolver can try the next one.
Points to cover, not a script. Say them in your own words and tie them to a system you have worked on.
On one page: the track cheat sheet.
Sources: RFC 1034: Domain names, concepts and facilities ↗ · RFC 9499: DNS terminology ↗ · Cloudflare: Announcing 1.1.1.1 ↗ · Report a problem
Diagrams are our own simulations: the timings, rates and counts in them are illustrative, not measurements. Captions are original wording.