A person comparing a simple domain-to-server diagram with a website loading on a laptop.
A DNS lookup matches a readable domain name with the network address a browser needs next. Vents Magazine editorial image.

People remember website names more easily than numerical network addresses. The Domain Name System connects those two forms. When a browser opens a domain, a DNS lookup usually helps it discover which server to contact.

The answer may already be nearby

The browser, operating system and local network often keep recent DNS answers in a cache. If a valid result is available, the lookup can end there. Reusing an answer saves time and reduces repeated requests across the network.

Cached records have a time limit chosen by the domain's operator. Once that period expires, the resolver asks again so changes can spread.

A resolver follows the hierarchy

If no cached answer exists, the device asks a recursive resolver, often provided by the network or selected by the user. The resolver can consult a chain of DNS servers.

Root servers direct it toward the servers responsible for a top-level domain. Those servers identify the authoritative name servers for the requested domain. The authoritative server returns the relevant record, such as an IPv4 or IPv6 address.

One name can involve several records

A domain may point to another hostname before reaching an address. Large services can return different servers based on region, availability or traffic. Separate records handle email delivery, verification and other functions.

This flexibility lets a readable name remain stable while infrastructure changes behind it.

DNS is only the beginning

Once the browser has an address, it still needs to establish a network connection, negotiate encryption when required, send an HTTP request and receive the page's files. A slow page is not necessarily a slow DNS lookup, though a failed lookup can prevent the connection from starting at all.

Encrypted DNS can protect the query while it travels between a device and its resolver, but the chosen resolver still processes the request. DNS turns a name into directions. It does not deliver the page itself; it tells the browser where the next part of the journey can begin.