The registrar sits at the registration layer

A domain registrar is the organization that sells and manages domain registrations for customers, called registrants. For generic top-level domains, ICANN maintains information about accredited registrars and notes that accredited registrars offer domain registration services with direct access to gTLD registries. You can browse the official list at ICANN’s accredited registrar directory.

The registrar is the place where you usually renew a domain, update name server delegation, manage transfer locks, and set some registration contacts. That does not mean the registrar hosts your website or your authoritative DNS zone, though some companies offer all of those services together.

Registrar vs. registry vs. registrant

These three terms sound similar, but they describe different roles. The registrant is the person or organization that registers the domain. The registrar is the company that provides the registration service. The registry operates the top-level domain itself, such as a gTLD or ccTLD namespace.

RoleMeaningExamples of responsibility
RegistrantThe customer using the domainChooses providers, renews domain, protects account access
RegistrarThe retail registration providerProcesses renewals, transfers, and name server delegation changes
RegistryThe operator of a TLDMaintains the authoritative database for that TLD

If you want to see which TLD operator is responsible for a given extension, the IANA Root Zone Database is a helpful reference.

What your registrar actually controls

Your registrar controls the registration relationship and certain metadata attached to it. Most importantly, it controls which authoritative name servers are published for the domain at the parent level. That is why changing providers often starts at the registrar: if the registrar still points to the old DNS host, the Internet keeps asking the old authoritative servers.

Registrars also often expose controls for transfer locks, auto-renew settings, DNSSEC DS record entry for supported domains, and contact or organization details attached to the registration. In short, registrars do not usually manage every DNS record in your zone, but they do control some of the knobs that determine which DNS host becomes authoritative in the first place.

Operational rule of thumb

If your zone file looks correct but the world still resolves old data, verify that the registrar is delegating the domain to the intended authoritative name servers.

Why registrar security is so important

Registrar access is high impact because a successful attacker may be able to change delegation, initiate transfers, or alter registration security settings. That is why organizations should treat registrar accounts as critical infrastructure. Strong passwords, multi-factor authentication, role separation, lock settings, and documented recovery contacts matter here as much as they do for cloud control planes.

From a DNS operations perspective, many severe outages are really registration-layer incidents. A domain can have perfectly healthy zone content at its authoritative provider and still fail globally if the registrar points to the wrong name servers or if a renewal lapses.

RegistrarDelegation, renewals, transfer settings
Authoritative DNS hostZone records and answers
Recursive resolverClient-facing lookups and cache

FAQ

Is my registrar automatically my DNS host?

No. It can be, but many organizations register domains with one provider and host authoritative DNS elsewhere.

Can I change registrars without changing my DNS records?

Usually yes, if the transfer preserves the same delegation and DNS hosting arrangement. The details depend on the TLD and providers involved.

When should I check the registrar during troubleshooting?

Any time name server delegation, renewals, transfers, or DNSSEC DS records might be involved.