General technology reading / 01
From a name to a network address
Illustrative line study
People use names to find websites. Networks use addresses to direct connections. The Domain Name System, usually shortened to DNS, connects these two ways of identifying a destination.
Following the lookup
A device can ask a recursive resolver for a DNS record. If the resolver does not already have a usable answer, it can follow referrals through the DNS hierarchy. An authoritative nameserver holds the relevant records for a domain. The answer travels back to the requesting device.
One step in a longer journey
Resolving a name does not itself download a page. After obtaining an address, the browser still needs to establish a connection and request content. That distinction helps explain why a name can resolve successfully while a website remains unavailable.
A useful thought experiment
Imagine a hypothetical reading club whose website moves to different hosting. The familiar name can stay the same while its address records change. Previously stored answers may remain in use until their allowed lifetime expires. The name, the lookup and the content host have different roles. When discussing a connection problem, identifying which role is involved is more useful than treating the whole journey as one event.
Further reading: Cloudflare’s DNS explanation.