NETWORKING / A CONCEPT NOTE
DNS
how names become IP addresses
Overview · mechanism
pitfall · examples
01 / THE SHORT VERSION
The idea in a few sentences.
The internet's phone book: you ask for supraj.dev, a chain of servers answers with 76.76.21.21. Everything else is caching and who gets asked.
02 / FOLLOW THE MECHANISM
How a lookup flows
Your machine
checks its own cache first — most lookups end here.
Resolver
(your ISP or 1.1.1.1) takes the question and does the legwork.
Root → TLD
servers point it toward whoever owns
.dev.Authoritative server
gives the real answer, cached for its TTL.
04 / COMMAND NOTES
Read the command, then the result.
Inspect the flags and arguments before trying an example. Snippets can need local setup, replacement values, or resources in your own environment.
just the answer, no noise
dig +short supraj.devwatch the full chain above, live
dig +trace supraj.dev05 / CHECK YOURSELF
Could you explain DNS to a teammate?
Try it out loud in two sentences: what it is, and the one detail that changes the picture. If you stall, the gap is the part to reread.
Up next in NetworkingTLShow encryption happens before the lock icon appears