Lesson 10 of 15
4. DNS

Memory card and where the analogy breaks

3 min read+10 XP

The memory card (tear this page out)

#QuestionMemory code
4.1Why names?Names for people, numbers for machines
4.2Parts of a domain?Right to left, big to small
4.3The lookup chain?Nobody knows everything; everyone knows who to ask next
4.4Record types?A for Address (quad-A for the four-times-longer IPv6), CNAME for 'call them instead', MX for Mail, TXT for proofs, NS for who's in charge.
4.5TTL and caching?TTL is the use-by date on a saved answer
4.6DNS load balancing, GeoDNS?DNS picks the city; the load balancer picks the counter
4.7Propagation?DNS doesn't spread, old copies expire. Lower the TTL before you move house.
4.8DNS failures?If DNS is down, you're down, even when everything is up

The whole chapter in one line: Ask the friend who knows who to ask, save the answer until its use-by date, and lower that date before you move.

Where the analogy breaks

  • Your phone's contacts are yours alone. A resolver's cache is shared by thousands of users, which is why one cached answer saves so many queries, and why one stale answer affects so many people.
  • Phone numbers belong to one phone. One domain name can point to many servers, and even give different answers to different people (4.6).
  • Your friend gives up if a directory is closed. DNS has many copies of every level, spread worldwide, so losing one server usually goes unnoticed. Losing a whole provider doesn't.

Quick check

Five questions on this chapter. Pick an answer, then check it.

quiz