How a Domain Turns Into a Website: DNS Basics

A domain name is what people casually call “the website name” — the address you type into a browser, like example.com. It’s human-friendly text, but computers don’t actually connect to “names”; they connect to numeric network addresses (IP addresses) or to other technical destinations that eventually resolve to an IP. A domain becomes useful only when the internet can translate that name into a destination.

A domain zone (often called a TLD) is the part after the last dot: .com, .io, .gr, .ru, etc. Thousands of domain zones exist to organize the global naming system: inside each zone, many second-level domains can be registered (for example, example inside example.com). Some countries use multi-level public suffixes like .co.uk, where registrations effectively happen one level deeper (for example, example.co.uk).

1) What DNS is

DNS stands for Domain Name System. The simplest way to think about it is: DNS is the internet’s address book.

• You know the “contact name”: example.com.
• DNS returns the “phone number”: an IP address like 203.0.113.10 (IPv4) or something longer for IPv6.
• Then your browser uses that result to connect to the right server and load the site.

Without DNS, a domain is just a paid-for label. You can own mybrand.com, but until DNS points it somewhere, visitors won’t reliably reach your server.

2) How the request flows when you type a domain

When someone types a domain in the browser, it roughly goes like this:

• The browser/OS asks: “Do I already know the answer?” (local cache).
• If not, it asks a DNS resolver (often your ISP, your mobile operator, or a public resolver).
• The resolver finds the authoritative DNS servers for that domain and asks them for the record.
• The resolver returns the answer to your device.
• The browser connects to the IP address (or follows an alias) and then loads the site over HTTP/HTTPS.

You don’t need to memorize these steps, but one key idea matters: there are multiple caches along the way, and they affect how fast changes appear.

3) The most common DNS records: A, AAAA, CNAME

Beginners usually meet these first because they directly control “where does the domain go?”.

A record (IPv4)

An A record maps a name to an IPv4 address.

Example idea (not a real IP):

• example.com → 203.0.113.10

Use A records when:

• you have a server IP from a VPS or dedicated server,
• your hosting provider tells you “point the domain to this IPv4”.

AAAA record (IPv6)

An AAAA record maps a name to an IPv6 address (newer addressing system).

Example idea:

• example.com → 2001:db8::10

Use AAAA records when:

• your provider gives you an IPv6 address,
• you want your site to be reachable over IPv6 (many modern networks support it).

Often a domain can have both A and AAAA. Devices that can use IPv6 may prefer AAAA; others will use A. That’s normal.

CNAME record (alias)

A CNAME record is an alias: it points one hostname to another hostname (not directly to an IP).

Example idea:

• www.example.com → example.com

or

• app.example.com → your-service.someprovider.com

Use CNAME when:

• a service tells you “create a CNAME to our hostname” (common for website builders, CDNs, analytics endpoints, verification setups),
• you want www to follow whatever example.com currently resolves to.

A practical benefit: if the target hostname changes its IP, you don’t need to update your DNS—your CNAME keeps pointing to the name, and the provider handles the IP changes behind it.

4) Why DNS changes “propagate” slowly (TTL and caching)

People say “DNS propagation”, but what you’re really seeing most of the time is caching.

DNS answers are stored temporarily to make the internet faster and reduce load. The rule that controls how long an answer may be cached is called TTL (Time To Live).

• TTL is a timer set on each DNS record.
• While TTL hasn’t expired, a resolver is allowed to reuse the old answer.
• Only after TTL expires will it ask again and pick up your new changes.

That’s why after you change records:

• it might work immediately for you (your network resolved the fresh value),
• but your friend in another country still sees the old site (their resolver has cached the old value).

Typical TTL behavior (what to expect)

• If TTL is high, changes can feel “slow”.
• If you lower TTL before a planned migration, the switch tends to be smoother because caches expire sooner.
• Even with a low TTL, you can still see delays due to extra caching layers (browser/OS, ISP resolver, corporate network DNS).

Common beginner scenarios (and which record to use)

• “I bought hosting and got an IP address.” - Usually you need an A record (and optionally AAAA if IPv6 is provided).
• “My site builder/CDN gave me something like project.hostingplatform.com.” - You’ll typically add a CNAME for a subdomain like www or app.
• “I changed DNS, but some people still see the old site.” - This is usually TTL/caching, not a broken website.
• “I want both example.com and www.example.com to work.” - Common approach: one points to the other (often www via CNAME), or both have appropriate A/AAAA records depending on your setup.