← Back to Hub / Networking

DNS Explained

The Domain Name System is the hierarchy of servers that translates human domains (google.com) into machine IP addresses (142.250.190.46).

🎭 Meet the Players (The Hierarchy)

DNS isn't one server; it's a team effort. Here is who handles your request.

🔍 Recursive Resolver

Usually your ISP or Google (8.8.8.8). This is your personal assistant. You ask it once, and it does all the running around to find the answer for you.

Analogy: The Librarian who knows where to look.

🌍 Root Server

The top of the pyramid. It doesn't know the IP, but it knows who manages the .com, .org, or .net registries.

Analogy: The Directory in the library lobby.

📂 TLD Server

Top-Level Domain Server. It manages specific extensions (like .com). It knows which specific company manages the domain you want.

Analogy: The Section Manager for "Fiction".

✅ Authoritative Server

The final destination (e.g., Route53, Cloudflare). It holds the actual "Zone File" with the IP address. It is the Source of Truth.

Analogy: The specific Book containing the answer.

🕹ī¸ Simulator: The Recursive Hunt

Mission: Find IP for blog.example.com
đŸ’ģ
Client
You
🔍
Resolver
ISP / 8.8.8.8
🌍
Root
Root Hint
📂
TLD
.com Reg
✅
Auth
Route53
SYSTEM Ready. Click 'Start Lookup' to trace the packet.

📝 The "Phonebook" Records

Type What it does Example Value
A Address. Maps a name to an IPv4 address. 142.250.190.46
AAAA Quad-A. Maps a name to an IPv6 address. 2001:0db8:85a3::8a2e:0370
CNAME Alias. Forwards one domain to another domain. www.example.com → example.com
NS Name Server. Points to the Authoritative server. ns-123.awsdns.com

💡 Pro Tip: This whole process takes milliseconds because servers Cache (TTL) the results.
The Resolver remembers "google.com = 1.2.3.4" for 5 minutes so it doesn't have to ask the Root every time.