Visualization: 1. The DNS Hierarchy (Recursive vs Authoritative)
Browser
example.com
Recursive
8.8.8.8
Root (.)
Find .com
TLD (.com)
Find NS
Auth NS
93.184.216.34
Press enter or space to select a node. You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.
Press enter or space to select an edge. You can then press delete to remove it or escape to cancel.
DOWNLOADING CONCEPT: 1. THE DNS HIERARCHY (RECURSIVE VS AUTHORITATIVE)...
↳DNS is a globally distributed database that translates domains (google.com) into IPs (142.250.185.46).
↳When your browser needs an IP, it asks a Recursive Resolver (like your ISP or 8.8.8.8).
↳The resolver does the heavy lifting: it queries the Root Servers (.), which refer it to the TLD Servers (.com), which finally refer it to the Authoritative Nameservers (the servers that actually hold the domain's records).
Command
dig +trace example.com Follows the exact path a recursive resolver takes, querying Root -> TLD -> Auth NS.
▲ LIVE INCIDENTUsers report they can't access the new website after we updated the IP address.
sre@arena:~/dns-routing
sre@arena:~$ dig A mywebsite.com && cat /etc/resolv.conf