Last Minute Notes
  • Github
  • Docs
  • Learn
    @sayanstwt
Lessons
0/37 done
  • DNS Resolution
  • Content Delivery Networks
  • Load Balancing
  • Gateways, Proxies & Meshes
  • Caching
  • Rate Limiting
Learn/System Design/Traffic & Edge

DNS Resolution

6 min Beginner 7 steps

How a name becomes an address, and why TTLs decide failover speed.

Browser has
a name
Network needs
an IP
Request
cannot leave
BrowserResolverAuthoritativeServer×GET api.shop.comno address yet: DNS must answer first
request reply failure
In this lessonStep 1 of 7
  1. The problem
  2. Resolve
  3. Records
  4. TTL
  5. Steering
  6. Failover
  7. Recap
Step 1 / 7problem

Names, not numbers

The browser knows api.shop.com. The network needs an IP address.

DNS maps names to addresses. It is the first dependency of almost every request, which makes it a hidden single point of failure.

Key idea

No DNS answer, no request. DNS is code you depend on.

←→ step·R replay·Space pause

You'll learn

  • Walk a name lookup from browser to authoritative server
  • Know what A, AAAA, CNAME, NS, MX and TXT records do
  • Choose a TTL: fast failover vs DNS load
  • Steer traffic with DNS, and know where it falls short
Read the full notesHLD Building Blocks, 2