Himanshu SharmaSoftware engineer
Let’s talk

How the Web Works · Lesson 6 of 15

Domain names, registries and registrars: who owns an address

Learn how a domain is registered and renewed, the difference between registry, registrar, DNS host and web host, and how to avoid losing a domain by accident.

12 minFinding the serverUpdated 14 November 2026

Awaiting technical review. This lesson is readable but not yet listed in search engines.

By the end of this lessonExplain who does what when you register a domain, separate registrar from DNS host and web host, and list the habits that protect a domain from lapsing or theft.

A name you rent, not a name you own forever

When you type a website's name, DNS does the lookup. But who decided that bakery.example belongs to this bakery and not to someone else? Domain registration. After this lesson you will know the parties involved, be able to tell registration, DNS hosting and web hosting apart, and have a checklist that protects a domain you care about.

The first surprise is that you do not buy a domain outright. You register it for a fixed period, which is chosen at purchase, and you must renew it to keep it. Pricing and the maximum period vary by registrar and by top-level domain, so check the details where you register rather than trusting a general rule.

The cast of characters

  • ICANN coordinates the naming system at the top and sets policy for many top-level domains. Some country-code domains have their own rules and managers.
  • Registry. The organisation that runs one TLD, such as .com or a country domain, and keeps the master list of names registered in it. It does not usually sell to the public.
  • Registrar. A company accredited to register names for customers and talk to the registry for you. This is the website where you pay and manage your domain.
  • Registrant. You, or your organisation: the holder of the registration.
  • Reseller. A company that sells registrations through a registrar. Fine, but know which registrar is behind it.

When you register bakery.example, the registrar tells the registry that this name now exists, who the holder is, and which name servers answer for it. The registry then publishes those name servers in its TLD, so the DNS lookups in DNS explained know where to go.

Three jobs that are often confused

Job What it does What it controls
Domain registration Holds the name in your account Ownership, renewal, which name servers are used
DNS hosting Runs the name servers with your records Where the name points: website, mail, verification
Web hosting Runs the server that answers requests The actual site files or application

One company can do all three, or you can split them. The key link is the name server setting at the registrar. It says "for this domain, ask these servers." Whichever service runs those servers is where you edit your DNS records.

This is a real delegation, seen in lookups captured on 2026-11 for example.com, a domain kept for documentation:

text
example.com.	31684	IN	NS	elliott.ns.cloudflare.com.
example.com.	31684	IN	NS	hera.ns.cloudflare.com.

The output shows the domain delegating its DNS to two name servers run by a service provider. Example output captured on 2026-11; yours will differ. It does not tell you who the registrar is: that is registration data, a separate record.

Pointing a domain at a site

Imagine you register bakery.example at registrar A, and rent hosting from company B, which gives you the address 203.0.113.10 (a reserved documentation address). The steps are:

  1. At the DNS host, add an A record for bakery.example with that address, and a CNAME or A record for www.
  2. Make sure the registrar's name server setting points at the DNS host you used.
  3. Wait for caches to expire, as the TTL lesson explained, then test.

Many hosting companies shorten this by offering their own name servers, so you only change the name server setting once.

Registration records and privacy

Domain registration data (holder, contacts, dates, name servers) was historically public through a service called WHOIS, and newer systems such as RDAP are replacing it. Because the data includes personal details, many registrars offer to substitute their own contact details in public view, and privacy law has pushed public records to show less. What you see differs by registrar and domain type. Whatever is public, keep the real contact email current, because renewal notices and transfer approvals go there.

Protecting a domain

Losing a domain can take a website and its email down together. These habits are widely recommended:

  • Enable auto-renew and keep a valid payment method on file, plus a calendar reminder as a back-up.
  • Use a strong, unique password and two-step sign-in on the registrar account. Whoever controls that account controls the domain.
  • Turn on the registrar lock (transfer lock), so the domain cannot be moved without your approval.
  • Use a role-based email address you will always have access to, not the inbox of someone who may leave.
  • Keep a record of where the domain is registered and where DNS is hosted. Many "mystery outages" are simply someone not knowing that.

Registrars typically give expired names a grace period before they are released, but the length and the cost to recover differ, so never rely on it.

Choosing a name

Short, easy to say and spell, and free of look-alike letters is a sound rule of thumb. Avoid names that are copies of someone else's brand, since trademark disputes are real. The choice of TLD is mostly a matter of audience and availability, and there is no verified rule here beyond what suits your readers.

Common mistakes

  • Letting the registration lapse because the renewal email went to an old address.
  • Editing DNS records at the registrar while the name servers actually point elsewhere, so nothing changes.
  • Sharing one registrar login among many people.
  • Registering through a third party who then holds the account in its own name, so you are not the registrant.
  • Deleting email records while changing the website's address.

Exercise

  1. Choose a domain you use (or example.com) and run dig NS yourdomain. Who runs its DNS?
  2. Draw three boxes: registrar, DNS host, web host. For a site you know, fill in who plays each role, or write "unknown".
  3. Write a five-line protection checklist for a domain you would not want to lose.
Show one possible answer
  1. The name servers listed. For example.com these were Cloudflare name servers in 2026-11.
  2. For a small site all three may be one company. If they differ, the NS records show the DNS host, the page's server header or address hints at the web host, and the registrar needs the registration lookup or your own account.
  3. Auto-renew on; two-step sign-in on; registrar lock on; contact email current and shared with a trusted second person; DNS and registrar details written down somewhere safe.

Key points

  • You do not buy a domain forever, you register it for a period and must renew it.
  • A registry runs a whole top-level domain, a registrar sells registrations to the public, and you are the registrant.
  • Registration, DNS hosting and web hosting are three separate jobs that one company may do or that three companies may share.
  • Keep contact details current, turn on renewal reminders and account protection, and use a transfer lock.

Check yourself

1. What is the registrant?
2. Which statement best describes the relationship of registry and registrar?
3. You register a domain with company A, host your site with company B and keep DNS with A. What must you do so visitors reach company B?
4. What is the main risk of not renewing?
5. Why is a transfer lock useful?