Back to roadmap
Module 4 · Edge: DNS, CDN, Load BalancersDay 02920 min

DNS Basics

How a name becomes an IP — and where each step can fail.

Day 029

DNS Basics

Client
client
Resolver
edge
Root
edge
TLD
edge
Authoritative
edge
Signal path
DNS resolution path
Client
client
flow
Resolver
edge
Resolver
edge
flow
Root
edge
Resolver
edge
flow
TLD
edge
Memory hook

DNS Basics: how a name becomes an ip

Mental model

move the first decision closer to the user

Design lens

Lower TTL increases query load on authoritative.

Recall anchors
RecordsHierarchyCaching

Why it matters

DNS is a hierarchical, cached name resolution system. A client resolver asks recursive resolvers, which walk the hierarchy until an authoritative server returns the answer; the answer is cached at every step for the TTL.

Deep dive

TTL chooses tradeoff: short TTL (60s) for fast failover, long TTL (1h+) for cache hit ratio and lower load.

DNS propagation isn't a network thing; it's caches and TTLs everywhere disagreeing.

Anycast is used by every major resolver and authoritative service to bring DNS within tens of ms globally.

Demo / scenario

Lower TTL before a planned IP migration.

  1. Today: TTL=3600.
  2. T-1d: drop TTL to 60.
  3. T0: change record to new IP.
  4. Old caches expire within ~60s; clients converge.

Tradeoffs

  • Lower TTL increases query load on authoritative.
  • Higher TTL increases convergence time on changes.
  • Always lower TTL ahead of changes, then raise back.

Diagram

Client
Resolver
Root
TLD
Authoritative
DNS resolution path.

Mind map

Check yourself

Loading quiz…

Sources & further reading