concept · beginner

Who controls each part of a domain

Separate the registrant, registrar, registry, DNS host, authoritative server, resolver, web host, CDN, and email provider.

The company that bills you for a domain may also host its DNS, website, or email, but those are separate jobs. Start by naming the job before deciding who controls it.

The control map

Role What it controls Where you usually make a change
Registrant The rights and responsibilities attached to the registration Registrar account and registration agreement
Registrar Registration transactions, renewal, contact data, transfer, and the nameservers submitted to the registry Registrar control panel or support
Registry operator The registration database and authoritative service for a top-level domain such as .com Usually through the registrar, not directly
DNS host The zone data for the domain DNS provider control panel or API
Authoritative server Answers from the zone data it serves Change the DNS host’s configuration, not the server response directly
Recursive resolver Finds and caches answers for a client Network, device, or resolver-provider configuration
Web host or origin Website files and application responses Hosting platform
CDN or reverse proxy Edge delivery, caching, TLS termination, and sometimes the public IP address CDN or proxy platform
Email provider Mailboxes, sending, receiving, and mail policy instructions Email platform plus the required DNS records

ICANN describes the registrant as the holder of rights to a registered domain, the registrar as the party that registers names for customers, and the registry operator as the maintainer of its top-level-domain registry [1]. DNS terminology distinguishes those registration roles from the systems that publish and resolve DNS data [2].

Registration does not host a website

Registering example.com establishes a renewable registration relationship. It does not automatically create:

  • an authoritative DNS zone;
  • an A, AAAA, or other record;
  • a web server or CDN configuration;
  • a TLS certificate; or
  • an email service.

A single vendor may bundle all of these, which makes the boundaries easy to miss. The boundaries still matter during migration and failure: changing a registrar is not the same operation as changing authoritative DNS, and changing DNS is not the same as moving a website.

Delegation connects registration to DNS hosting

For a typical registered domain, the registrar sends the chosen authoritative nameserver set to the registry. The parent zone publishes that delegation. The DNS host serves the child zone from those nameservers.

That creates two places to inspect:

  1. the parent-side delegation, controlled through the registration path;
  2. the child-zone data, controlled at the DNS host.

They can disagree. Editing NS records inside the child zone alone usually does not replace the parent delegation.

Resolution is another control plane

A recursive resolver acts for a client. It follows referrals, validates DNSSEC when configured to do so, and caches responses. The resolver does not control the authoritative zone, and a cached resolver answer does not prove what every other resolver currently holds.

When two users see different answers, record:

  • the exact queried name and record type;
  • the recursive resolver used;
  • the observation time;
  • the authoritative answer; and
  • the relevant TTL.

This separates authoritative configuration from cached observations.

Diagnose by asking who owns the next setting

Use this sequence:

  1. Registration problem? Check the registrant account, registrar, registry, status codes, and renewal state.
  2. Delegation problem? Compare the parent nameserver set with the intended authoritative service.
  3. Record problem? Check the DNS host and query its authoritative servers.
  4. Cached answer? Identify the recursive resolver and TTL before changing authoritative data again.
  5. DNS answers correctly? Continue at TLS, HTTP, CDN, origin, or email instead of making speculative DNS changes.

The useful question is not “Who is my domain provider?” It is “Who controls the specific setting that the evidence says is wrong?”

Next step

Follow a lookup from the recursive resolver to the authoritative answer to see how these roles interact on the wire.