SOLID STATE PRESS
← Back to catalog
How DNS Works: The Internet's Phone Book cover
Coming soon
Coming soon to Amazon
This title is in our publishing queue.
Browse available titles
Computer Science

How DNS Works: The Internet's Phone Book

Root Servers, Recursive Resolvers, and the Cache That Runs the Web — A TLDR Primer

You typed a web address, hit enter, and a page loaded — but what actually happened in between? If your networking class or textbook buries the answer under jargon about root zones, TTLs, and resolver chains, this primer gets you oriented fast.

This TLDR guide walks through how the internet finds websites, starting with the basic problem DNS solves: humans think in names, computers route by numbers. From there it traces the path a real lookup takes — your browser, your resolver, the root servers, the top-level domain servers, and the authoritative server that finally hands back an answer. Along the way you'll learn to read the DNS record types that route web traffic and email, understand why caching makes the whole system fast, and why an update to a domain can take hours to show up everywhere (the mysterious 'propagation delay').

A closing section covers the security side: how classic DNS can be spoofed, and how DNSSEC, DNS-over-HTTPS, and DNS-over-TLS were built to fix it — material that shows up constantly in computer science and networking coursework.

Written for high school and early-college students who need a computer networking study guide that skips the theory-heavy detour and gets straight to what's testable and useful. No filler, no fluff — just the concepts explained clearly, with the kind of concrete walkthrough a distracted 11pm-before-the-quiz brain can actually absorb.

Open it, read it, understand DNS. Then go ace the quiz.

What you'll learn
  • Explain why DNS exists and what problem it solves
  • Trace a full DNS query from browser to authoritative server
  • Identify the roles of root, TLD, and authoritative name servers
  • Read common DNS record types (A, AAAA, CNAME, MX, NS, TXT)
  • Understand caching, TTLs, and why DNS changes take time to propagate
  • Recognize security issues like DNS spoofing and how DNSSEC and DoH address them
What's inside
  1. 1. Why DNS Exists: Names vs. Numbers
    Introduces the core problem DNS solves — humans use names, computers use IP addresses — and sketches the history from HOSTS.TXT to a distributed system.
  2. 2. The DNS Hierarchy: Roots, TLDs, and Authoritative Servers
    Explains the tree structure of the DNS namespace, the 13 root server clusters, top-level domains, and how authority is delegated down to individual domains.
  3. 3. Anatomy of a DNS Query: From Browser to Answer
    Walks through a full recursive lookup step by step, showing what your computer, resolver, and each server in the chain do to resolve example.com.
  4. 4. DNS Records: The Data Behind the Names
    Covers the most important record types students will encounter and how they combine to route web, email, and other services.
  5. 5. Caching, TTLs, and Why Changes Take Time
    Explains how caching at every layer keeps DNS fast, what TTL values mean, and why 'DNS propagation' can take hours after an update.
  6. 6. Security and the Modern DNS: Spoofing, DNSSEC, and Encrypted Lookups
    Introduces the main security weaknesses of classic DNS and the protocols developed to fix them, including DNSSEC, DoH, and DoT.
Published by Solid State Press
How DNS Works: The Internet's Phone Book cover
TLDR STUDY GUIDES

How DNS Works: The Internet's Phone Book

Root Servers, Recursive Resolvers, and the Cache That Runs the Web — A TLDR Primer
Solid State Press

Contents

  1. 1 Why DNS Exists: Names vs. Numbers
  2. 2 The DNS Hierarchy: Roots, TLDs, and Authoritative Servers
  3. 3 Anatomy of a DNS Query: From Browser to Answer
  4. 4 DNS Records: The Data Behind the Names
  5. 5 Caching, TTLs, and Why Changes Take Time
  6. 6 Security and the Modern DNS: Spoofing, DNSSEC, and Encrypted Lookups
Chapter 1

Why DNS Exists: Names vs. Numbers

Every computer on the internet has an address, but it's not the kind you'd want to memorize. When you type google.com into a browser, your computer doesn't actually talk to "google.com" — it talks to a machine at an IP address, a numerical label like 142.250.80.14 that identifies exactly where a device lives on a network. Names are for humans. Numbers are for machines. DNS, the Domain Name System, is the translation layer that lets you use the first while your computer uses the second.

IP addresses come in two flavors. IPv4 addresses look like 142.250.80.14 — four numbers from 0 to 255, separated by dots, giving about 4.3 billion possible addresses. That sounds like a lot until you remember there are billions of phones, laptops, servers, and smart doorbells all needing their own address. IPv4 addresses ran low years ago, which is why the internet also uses IPv6, a newer format with a vastly larger address space, written in longer strings like 2607:f8b0:4004:c07::64. Both formats do the same job — uniquely identifying a device — they just differ in how many addresses they can express.

The human-friendly name you type instead of an IP address is called a hostname — www.google.com, example.com, mail.yahoo.com. A hostname is easier to remember, easier to type, and doesn't change even if the underlying server does. That last point matters: a company can move its website to a new server with a new IP address without anyone needing to learn a new name. The hostname stays stable; the number behind it can shift. This separation of "name" from "location" is the entire reason DNS exists.

About This Book

If you're a computer science student studying for a networking exam, a self-taught coder trying to understand how the internet finds websites, or a parent helping with homework on computer networks, this book is for you. It's also for anyone who's ever wondered how does DNS work explained simply, without wading through a textbook chapter.

This guide walks through the full DNS lookup process for students who need the concepts fast: the hierarchy of root servers and resolvers explained step by step, what happens between typing an address and loading a page, and what is a DNS record explained in plain terms — A, CNAME, MX, and more. It also covers caching, TTLs, and modern security topics like DNSSEC and encrypted DNS. Think of it as a computer networking study guide built for computer science exam prep basics — concise, with no filler.

Read it straight through first. Then work the examples and try the problem set at the end to check what stuck.

Keep reading

You've read the first half of Chapter 1. The complete book covers 6 chapters — readable in one sitting.

Coming soon to Amazon