How DNS Works: an editable mindmap
Explore How DNS Works as an editable mindmap. Follow color-coded branches for Browser & name, Resolver cache, Delegation, Answer, with supporting ideas and curved connections.
A mindmap of How DNS Works, with the main ideas arranged around a central topic and connections that show how they relate.
How DNS Works: an editable mindmap
The interactive MindMap canvas for this explanation — every lane, row and arrow above is a real QueryChart diagram you can open and edit.
How to read this mindmap
- Begin at “How DNS Works” in the centre, then explore any branch that answers your question. The branch colors keep each group of ideas together.
- Curved lines show relationships; arrowheads appear only where one idea leads to another. Select any idea in the editor to change its text, position, or connections.
Browser & name
This branch brings together “You type a domain, e.g. querychart.io”, “Browser sends the query to a recursive resolver”.
Resolver cache
This branch brings together “The recursive resolver (usually run by your ISP or a public DNS service) remembers answers for the time-to-live the record declares, which is why repeat lookups are near-instant.”, “Resolver caches the answer and returns it”.
Delegation
This branch brings together “Resolver asks the root server”, “Root server points to the .io TLD server”, “TLD server points to the authoritative server”.
Answer
This branch brings together “The authoritative name server is the domain owner's own server — it holds the final record and is the only one that can answer authoritatively.”, “Browser connects to the IP address”.
Connections across the map
DNS is a delegated chain: root points to TLD, TLD points to authoritative, and only the authoritative server holds the final record.
The recursive resolver does the work once and caches the answer, which is why repeated lookups are near-instant.
The domain holder controls only the authoritative server, not the root or TLD servers.
A lookup failure anywhere in the chain means the browser has no destination and no request is sent.
DNS resolution precedes every connection, which is why it is the first hop in the API request lifecycle.
Key relationships and takeaways
- DNS is a delegated chain: root points to TLD, TLD points to authoritative, and only the authoritative server holds the final record.
- The recursive resolver does the work once and caches the answer, which is why repeated lookups are near-instant.
- The domain holder controls only the authoritative server, not the root or TLD servers.
- A lookup failure anywhere in the chain means the browser has no destination and no request is sent.
- DNS resolution precedes every connection, which is why it is the first hop in the API request lifecycle.
When to use this visual
- Explaining to a new team member why a domain is slow to resolve the first time and instant afterwards.
- Debugging a "site not found" report by walking the chain (cache, authoritative records, TTL) instead of guessing.
- Teaching the ownership model: which DNS records your team controls versus the registrar or hosting provider.
How it works
Start at the central topic
Rename “How DNS Works” if you want to adapt this map to a specific project or lesson.
Develop the branches
Edit the supporting ideas, then add examples and notes where a branch needs more detail.
Connect related ideas
Draw curved connections across branches; use an arrow only when the relationship has a direction.
Frequently asked questions
What is DNS in simple terms?
DNS, the Domain Name System, is the directory that turns a domain name like querychart.io into the IP address a computer can connect to. It works by delegation: a chain of servers, each responsible for one part of the name, that together produce the final address. Without it you would have to remember and type IP addresses.
What is the difference between a recursive resolver and an authoritative server?
The recursive resolver is the server your device asks; it does the searching, follows the chain on your behalf and caches the result. The authoritative server is the domain owner's own server and the source of truth for that domain: it holds the final records and is the only server that can answer authoritatively. The visual places them at opposite ends of the chain for exactly this reason.
Why is DNS cached and what is a TTL?
Caching is what keeps DNS fast: without it every page load would trigger a full chain of lookups. Every DNS record carries a time-to-live (TTL) saying how long a resolver may remember it. The cache decision in the visual is that mechanism: when a record's TTL expires, the resolver must walk the chain again.
What happens when DNS fails?
If no server in the chain can produce an answer, the resolver returns an error and the browser shows the domain cannot be reached. The usual causes are a missing or mistyped record on the authoritative server, an expired domain, or a resolver that cannot reach the chain. Walking the lookup order in this visual is a practical way to find which of those it is.
Edit this mindmap in QueryChart
Open this mindmap as your own editable free canvas. Move ideas, add branches, and draw new connections.