Domains Navigator domainsnavigator
English

Domain guides

Who manages internet domains?

No single company owns the domain name system. It works as a chain of responsibility: IANA records who operates each top-level domain, registries maintain the authoritative lists, and registrars deal with people and businesses buying names.

The root zone is a directory, not a domain shop

IANA maintains the Root Zone Database. Open the entry for .pl and it identifies NASK as the sponsoring organisation; the .de entry points to DENIC, while .uk is managed by Nominet. These records answer the basic question “who is responsible for this extension?” but IANA does not normally sell a domain to an end customer.

The root server system is often described as 13 servers. More precisely, DNS uses 13 named root-server identities, labelled A through M, which are delivered by many physical instances around the world. That distinction matters: the system is distributed rather than sitting in one building.

ICANN coordinates policy; registries run extensions

ICANN coordinates important parts of the global naming system and accredits registrars for generic domains such as .com. A registry has a narrower operational job: it maintains the authoritative database for one extension or a group of extensions and publishes its registration rules.

Country-code registries have substantial independence. DENIC can set procedures for .de, NASK for .pl, and Nominet for .uk. This is why advice such as “every expired domain has the same 30-day grace period” is unsafe. The answer has to come from the policy of the exact extension.

The registrar is the company on your invoice

A registrar provides the search box, checkout, control panel, renewal notices and customer support. It sends accepted data to the registry. Two registrars selling the same .com name are not selling different technical products, but their prices, support and account security can differ sharply.

When something goes wrong, contact the right level. Billing, passwords and transfer codes belong with the registrar. A registry can clarify policy or correct a registrar-level failure under its procedures. IANA is useful for identifying the registry, not for resetting a retail account.

The holder still has work to do

The registrant—called the abonent in NASK’s Polish terminology—is the person or organisation holding the contractual right. Keep its details current, use two-factor authentication and make sure renewal messages reach an inbox controlled by the organisation, not a former employee.

For a business-critical name, record four things outside the registrar panel: the registry, registrar, renewal date and recovery contact. This short inventory becomes valuable when a card expires, an employee leaves or a supplier relationship ends.

A useful escalation order

Start with the registrar for account, payment and transfer problems. Check the registry policy when the question concerns eligibility or expiry. Use the IANA record to identify the responsible registry. This order avoids sending a retail support request to an organisation that never held the customer account.

Reviewed: 28 August 2026 · DomainsNavigator Editorial Team