Synarkview

A little curiosity goes a long way.

← All explanations
S / 02/Technology/System map

How does a name find a website?

From a familiar address to a server: meet the lookup that gets you to the right place.

Explore in 6 steps ↓Scope & source ↗
ONE CONNECTION AT A TIME

LET’S TAKE
A CLOSER LOOK.

Choose a step or follow the sequence.
The complete explanation is here, too.

S / 02/System mapSOURCE-LINKED EXPLANATION
NAME → DNSADDRESSCONNECT →A simplified model. Follow the highlighted part.
DOMAIN01 / 06

Begin with a name

A domain gives people a readable name instead of asking them to remember an IP address.

  1. 01 / DOMAIN

    Begin with a name

    A domain gives people a readable name instead of asking them to remember an IP address.

  2. 02 / CACHE

    Check what is already known

    Your device may already have a usable answer in its cache. If so, the lookup can finish quickly.

  3. 03 / DNS

    Ask for an address

    If no cached answer is available, a DNS resolver helps find the address associated with the name.

  4. 04 / ADDRESS

    Receive the answer

    The answer provides an address the device can use. Names and addresses are related, but they are not the same thing.

  5. 05 / CONNECT

    Connect to the server

    With an address available, the browser can establish the connections needed to request the website.

  6. 06 / WEBSITE

    Keep the roles separate

    DNS finds an address. The web server supplies the website. A successful lookup alone does not guarantee the website is available.

THE EDGES OF THE PICTURE

What this model covers.

A simplified DNS lookup. Caches can skip steps; a domain may resolve to multiple addresses. DNS lookup and loading a website are separate operations.

GO TO THE SOURCE · OPENS A NEW TABMDN · What is a domain name?

An authored visual explanation. The illustration is a metaphor; the steps describe a simplified model.