About this tool
DNS is the address book your device consults before contacting a website. This visual simulator follows a lookup through the resolver and DNS hierarchy. It helps beginners connect a familiar website name to an IP address, while showing the difference between recursive requests and iterative referrals. Everything shown is a teaching scenario, not a live lookup.
How it works
- Choose a recursive, iterative or missing-name scenario.
- Play the sequence and follow the request between the displayed servers.
- Inspect the packet fields and the answer or referral at each stage.
- Compare the cache display with the full resolution chain.
Worked example
Suppose www.example.com has an A record of 192.0.2.10 with a TTL of 300 seconds. An uncached resolver follows root, .com and authoritative referrals to obtain that record. It can reuse the answer during the remaining TTL instead of repeating the full chain.
Common mistakes
A root server normally provides a referral, not the website's final address. DNS does not fetch the web page. Avoid assuming every visit repeats all these messages: browser, operating-system and resolver caches can shorten the process.
FAQ
Does DNS always use UDP?
No. Traditional DNS commonly uses UDP port 53, but TCP port 53 is also used, including when a UDP response is truncated. Encrypted DNS transports are separate options.