← Back to Learning Hub

DNS Migration • Intermediate • 6 min read

Registry, Registrar, and Reseller: Who Controls Your Domain

The control chain behind a domain: registry, registrar, and reseller, who holds the authoritative record, and who to escalate to when a change will not stick.

When a domain change will not stick, or a transfer stalls, or you cannot work out who is actually in charge of your name, the usual cause is confusion about the chain of control behind every domain. Three distinct parties sit between you and the authoritative record: the registry, the registrar, and sometimes a reseller. Each holds a different piece of authority, and knowing which one to contact is the difference between a ten minute fix and a week of forwarded tickets. This guide explains who does what, who holds the authoritative data, and how to escalate when a change refuses to take effect.

The three parties and what each one owns

The simplest way to understand the chain is to see it as a hierarchy of authority. The registry sits at the top and operates the top-level domain. The registrar is accredited to sell names in that TLD and to push changes into the registry on your behalf. A reseller, when one is involved, is a company that sells the registrar's service under its own brand without being accredited itself. You, the registrant, are the legal holder of the name but you do not talk to the registry directly.

PartyRoleHoldsYou contact them
RegistryOperates the TLD and its master databaseThe authoritative record for every name in the TLDAlmost never, only through a registrar
RegistrarAccredited seller, writes changes to the registryYour account, auth code, contact and nameserver dataFor most changes and all transfers
ResellerRebrands a registrar's serviceYour billing and login, but not registry accessFirst, for day-to-day support
RegistrantLegal holder of the domainThe rights to the nameThis is you

Who holds the authoritative record

The registry database is the single source of truth for a TLD. It is sometimes called the thick or thin registry depending on how much contact data it stores, but in every case it holds the definitive answer to who the sponsoring registrar is, which nameservers are delegated, and what the domain's status codes are. Your registrar maintains its own copy of your settings and is the only party permitted to write changes into the registry for your name. This is why a setting that looks correct in a reseller panel can still be wrong at the registry: the change has to travel all the way up the chain to become real.

How a change travels up the chain

Picture updating your nameservers when you buy through a reseller. You enter the new nameservers in the reseller's control panel, the reseller's system relays that to the accredited registrar, and the registrar sends an EPP command to the registry, which updates the authoritative delegation. Only after that last step does the wider internet see the new nameservers. If any link breaks, for example the reseller queues the request but never forwards it, your change appears saved on screen yet never reaches the registry. This flow tells you exactly where to look when something does not take effect.

Reading the chain from a WHOIS record

You can see most of this hierarchy in a domain's public record. The sponsoring registrar is listed explicitly, usually with an IANA ID number that identifies the accredited company even when you bought through a reseller whose name appears nowhere. The status codes reveal what the registry or registrar has locked. The nameservers show the current delegation. A reseller, by contrast, is typically invisible in WHOIS, which is a common surprise: people buy from one brand and find a completely different accredited registrar named in the record.

  1. Look up the name and find the "Registrar" field and its IANA ID. That is the accredited party, regardless of who you paid.
  2. Check the status codes to see whether a lock is blocking the change you are trying to make.
  3. Note the listed nameservers and compare them to what you expect.
  4. If the registrar named is one you have never heard of, you most likely bought through a reseller of theirs.
  5. Run the name through a WHOIS search to confirm all of the above from the authoritative data rather than a billing panel.

Where control actually matters

The chain becomes concrete at three moments: transfers, recovery, and dispute. For a transfer, the losing registrar holds your auth code and transfer lock, so a reseller must relay to the registrar. For account recovery, only the accredited registrar can prove and reset control, which is why a defunct reseller can leave you stranded even though the registrar behind it is healthy. For a formal dispute or legal hold, the registry can act through its relationship with the registrar. In all three, authority flows from the registry down, and your leverage is strongest with whoever is one step closer to the registry than your current blocker.

How to escalate when a change will not stick

When something refuses to take effect, escalate along the chain in order rather than jumping to the top. Start with the party you bought from, then move up only when they cannot resolve it.

  1. Contact the reseller first if you bought through one. Give them the exact change and a screenshot showing it saved on their panel.
  2. Identify the accredited registrar from WHOIS and open a ticket with them directly, referencing the domain and the IANA ID.
  3. Ask the registrar to confirm the change reached the registry, not just their own system. This is the question that exposes a stuck relay.
  4. If the registrar is unresponsive and the matter is serious, the registry's or ICANN's complaint processes exist for accredited-registrar failures.
  5. Keep the auth code and account email current throughout, since both are needed to prove control at every level.

Do I ever contact the registry directly?

Almost never for ordinary changes. Registries work through accredited registrars by design, so your route to the registry is your registrar. Direct registry contact is reserved for operators and for specific dispute processes.

Why does WHOIS show a registrar I never signed up with?

Because you most likely bought through a reseller. Resellers rebrand an accredited registrar's service, so the record names the registrar behind them, not the brand you paid. The IANA ID in the record identifies that accredited party.

Can a reseller complete my domain transfer?

Not on its own. The auth code and transfer lock live with the accredited registrar, so a reseller can only relay your request. If the reseller's relay is broken, you deal with the registrar directly, as covered in our guide to transferring a domain between registrars.

My reseller went out of business. Have I lost the domain?

Usually not. The name is still registered through the accredited registrar, and you can regain control by proving ownership to that registrar. The reseller held your billing and login, but not the registration itself.

Who decides my domain's status codes?

Both the registrar and the registry can set status codes, which is why some begin with "client" and others with "server." The registrar sets client codes on your account; the registry sets server codes at the TLD level. Either can block a change you are trying to make.

The control chain decides who can fix what, and matching your request to the right party is the fastest way out of a stuck change. For the transfer-specific mechanics of locks and auth codes, see our guide on transferring a domain between registrars, and for what happens when a name lapses, our walkthrough of the domain lifecycle after expiry.

Troubleshooting box

If results look inconsistent, compare authoritative nameservers first, then recursive resolvers by region. Capture snapshots every 10 minutes for deterministic incident timelines.

Try VallaDNS free →

Intermediate • 6 min

How to Find a DNS Record's TTL (Current Value)

Find the TTL currently set on a DNS record: read the TTL column in dig and nslookup, tell the authoritative TTL from a resolver's countdown, and confirm a change.

Intermediate • 7 min

How to Check If Nameservers Have Propagated

Nameserver changes live at the parent TLD and follow the registry NS TTL, not your zone. Check the parent delegation and confirm the new NS set worldwide.