Select Resolution Type
Recursive DNS Resolution
The client delegates all work to a Recursive Resolver. The resolver contacts Root, TLD, and Authoritative servers on the client's behalf — the client simply waits for the final IP answer.
Mode:
Client
Needs example.com
Recursive Resolver
The Middleman
Root Server
Refers to .com TLD
TLD Server
Refers to Auth NS
Authoritative NS
Knows final IP
Activity Log
RECURSIVE_TRACE
- Choose a mode and click Start Simulation.
Recursive — How it works
- Client sends one query to the Recursive Resolver
- Resolver queries Root → gets referral to TLD
- Resolver queries TLD → gets referral to Auth NS
- Resolver queries Auth NS → gets the final IP
- Resolver caches & returns IP to the Client
Client burden: minimal — one query, one answer.
Iterative — How it works
- Client queries Root Server directly
- Root returns a referral to the TLD server
- Client queries TLD Server directly
- TLD returns a referral to the Auth NS
- Client queries Auth NS → gets the final IP
Client burden: high — must follow every hop.
R
Recursive Query
Client asks Resolver: "Get me the answer." The resolver does all the work and returns the final IP.
I
Internal Iterative
The resolver itself uses iterative queries (Root→TLD→Auth) internally while the client waits.
C
Caching
The resolver caches the result for the record's TTL, skipping the full hierarchy on repeat queries.