Week 9 · Lesson 2

DNS (1): Names to Addresses

You can remember a name like www.example.com; a router cannot route to a word. The Domain Name System (DNS) is the distributed phone book that translates human names into the IP addresses the network actually uses — and it does it without any single database holding everything.

CCNA 200-301 Domain 4.0 IP Services Verified 2026-10-11
Part 1

The DNS problem, and a distributed client–server service

Networks route on numbers. Every device is found by its IP address — 93.184.216.34 (IPv4) or a long hexadecimal IPv6 address — but people are terrible at remembering numbers and excellent at remembering names. The DNS problem is that mismatch: humans use names, networks use IP addresses.

Definition — DNS. The Domain Name System is a distributed, hierarchical name service that maps human-friendly domain names (like www.example.com) to the IP addresses (like 93.184.216.34) that routers need. It is defined by RFC 1034 (concepts) and RFC 1035 (implementation).

Why distributed? A single central database holding every name on the Internet would be a single point of failure, would need to be copied to every client, and would be an unmanageable bottleneck. Instead, the name space is split into zones, each zone is owned by a different organisation, and each organisation runs authoritative name servers for its own zones. No one server knows everything — but together they can answer anything.

DNS is classic client–server. The resolver is the client side: it asks questions. The name server is the server side: it answers. On a typical PC the stub resolver (inside the operating system) sends each query to a local DNS server — usually your home router (acting as a DNS forwarder) or your ISP’s resolver, sometimes a public one such as 8.8.8.8.

RoleWhoWhat it does
Stub resolverInside your OS / appFormats each query and sends it to the configured DNS server
Recursive resolverISP / public / corporate serverDoes the full search on your behalf and returns the final answer
Root / TLD / authoritative serversIANA, registry operators, domain ownersRespond to iterative queries with referrals or final answers
Exam tip. In client–server terms, the resolver is the client. When a question says “your PC asks the DNS server for an address”, the PC is the client (resolver) and the DNS server is the server. This mirrors Lesson 1’s client–server model exactly — DNS is simply one service (port 53) riding on that architecture.
Part 2

The three layers: root, TLD, authoritative

Think of the DNS hierarchy as a tree. Reading a name from right to left climbs the tree from the most general to the most specific. For www.example.com. the FQDN (fully qualified, ending in a dot) has the label chain www → example → com → <root>.

The DNS tree · select a layer
Root servers 13 identities, A to M TLD server — .com Authoritative — example.com A record: www = 93.184.216.34 Knows who serves .com Knows who serves example.com Holds the final answer www.example.com. read right to left

Memory hook. Each layer answers one question about the layer below it: root → “who serves .com?”, TLD → “who serves example.com?”, authoritative → “what is www.example.com?” The resolver works its way down the tree one level at a time.
Part 3

Resolution flow for www.example.com

Here is the complete journey, in order. Step through it and watch the query type change from recursive at the client edge to iterative between the servers.

Resolution step by step
1 / 5

      

Steps 2–4 are iterative queries: each server answers the resolver with the next best thing it knows, and the resolver follows up. Step 1 (and the final delivery) are recursive: the client asks the resolver to do the whole job and return one answer.

Part 4

Recursive vs iterative queries

Query typeMeaningWho sends it
Recursive“Do everything, come back with the final answer.” The server must not respond with a referral.Client resolver → recursive DNS server
Iterative“Give me the best answer you have now; if it’s a referral, I’ll ask the next server myself.”Recursive resolver → root, TLD, authoritative servers
Who asks whom? · select the query type
Your PC Resolver Root TLD .com Authoritative

Exam tip. Two synonyms to keep glued together: recursive = client–server = “find me the answer”; iterative = server-to-server = “point me to the next server”. A common trap is “which query does your PC send?” — the PC always sends a recursive query to its local/recursive resolver. The iterative queries happen between DNS servers, in the background, before your PC ever sees the answer.
Part 5

Caching, TTL, and redundancy

DNS would collapse under its own load if every query travelled the whole tree. Resolvers therefore cache every answer and referral they receive, inside their TTL window. Move the slider and watch what a second lookup costs.

Cache lifetime · set the TTL and the elapsed time

A server serving a successful lookup sets the query’s TTL (a countdown remaining; the authoritative server fixes values like 300 seconds); for a cache to serve a cached record, it must use the (possibly decremented) TTL. Every DNS server at every level caches:

“...and it’s the TTL”. Almost every DNS “why is the change not showing” complaint is the cache: an admin lowers a server’s TTL before changing records precisely so stale cached copies expire quickly. When an exam question says “changes will not be visible for a while”, cite the TTL of the cached record.

Redundancy: 13 root identities and anycast

The root is the single most load-bearing part of DNS, so it is built for redundancy at two levels:

TTL servers and authoritative zones are likewise replicated: every authoritative zone is required (RFC 1034/1035) to have more than one name server, and the resolver moves on to the next NS if one fails. This redundancy is why DNS almost never “goes down” globally.

Part 6

URL vs hostname vs FQDN

Three strings the exam loves to splice apart. Pick one below and see how it is named.

Which name is this? · select a string

TermWhat it isExample
URLThe full locator: scheme + authority + path.https://www.example.com/index.html
FQDNThe Fully Qualified Domain Name: the complete, absolute name ending with the root dot; no scheme, no path.www.example.com.
HostnameOne label of the FQDN (worst, the leftmost), for example “www”; colloquially people say “hostname” for the whole name.www (a label), or loosely www.example.com
Exam tip. The most exam-friendly definitions: the hostname is a single label (“www”, “mail”, “ns1”); the FQDN is the complete dotted name with a trailing root dot (www.example.com.); the URL adds the scheme and path (https://…). If a question gives three strings and asks which DNS would resolve, DNS resolves the FQDN, not the URL or bare hostname.
Part 7 · Your turn

Review

Check what you have learned with these review questions.

Review · 6 questions

Sources

Sources & references

  1. Mockapetris, P. RFC 1034: Domain Names — Concepts and Facilities (1987), defines the name space, delegation, and authoritative zones. rfc-editor.org/rfc/rfc1034.
  2. Mockapetris, P. RFC 1035: Domain Names — Implementation and Specification (1987), defines message format, port 53 transport, and resource records. rfc-editor.org/rfc/rfc1035.
  3. IANA. Root Servers (the A to M identities and the root zone). iana.org/domains/root/servers.
  4. Hoffman, P., Sullivan, A. & Fujiwara, K. RFC 7719: DNS Terminology (2019), authoritative definitions of resolver, recursive, iterative and FQDN. rfc-editor.org/rfc/rfc7719.
  5. Cisco. CCNA (200-301) Exam Topics, IP Services — DNS. cisco.com.

Target exams: CCNA 200-301 v1.1 · CyberOps Associate 200-201. Last content verification: 2026-10-11.