.comwww A203.0.113.10
A recursive DNS lookup for www.example.com. Your laptop asks its resolver once, with recursion desired; the resolver then asks a root server, a .com server and example.com's name server in turn, carrying the question as an envelope. The root and .com servers pop referral cards onto it (NS plus glue), the authoritative server pops the answer card (AA), and the resolver files each record set in a cache drawer for its own TTL, which the clock on its lid shows. Asked again 600 s later by a second device, it answers from the drawer with no server queries: 21 ms instead of 141 ms. Shown with the full question at every hop (RFC 1034). Resolvers using QNAME minimisation (RFC 9156) send only "com." to the root and "example.com." to the .com server, revealing less of the name. Latencies are illustrative one-way times, not measurements. a.root-servers.net 198.41.0.4 and a.gtld-servers.net 192.5.6.30 are real; ns1.example.com 192.0.2.53 and 203.0.113.10 are RFC 5737 documentation addresses. The .com delegation for example.com and the example.com zone are illustrative; the live example.com is delegated to two Cloudflare nameservers, which have no in-zone glue. The root tower's 13 lights are the named identities a–m.root-servers.net, each served by many anycast instances.

Cold lookup · 141 ms illustrative

  1. The browser and then the operating system look for a cached answer for www.example.com and find none.

Look up again · 600 s later · 21 ms

The message, dig-style

;; step 1 · local-cache · cache · local
;; at the stub resolver
;; QUESTION SECTION:
;www.example.com. IN A

Real referrals carry all 13 .com nameservers (a–m.gtld-servers.net) and their glue; one of each is shown. DNS falls back to TCP port 53 when a response is too large for UDP (TC=1).