Encyclopedia Ethereum · Entry 241
ENS owner, manager and resolver: who controls which settings?
In this article
At a glance
Key facts
| Fact | Detail | Source |
|---|---|---|
| Registration | The registrar tracks registration ownership and expiry. | [1] |
| Management | The manager can edit records subject to the name’s control rules. | [1] |
| Resolver | The resolver is a contract serving records, not necessarily the owner. | [1] |
Identify the actual authority you need
An ENSv1 .eth registration belongs to the registrar’s ownership system. The registry maintains the name’s control and resolver pointer. Resolver records then determine such information as the address returned for a payment.
Interface labels can simplify these layers. Read which operation you are performing: transfer registration, change management, change resolver or edit a record.
A payment address is not automatically the owner
Suppose a group owns a name through one account but points its ETH record to a treasury account. Sending a payment to the name uses that treasury record. It does not prove the treasury account can transfer the registration.
Likewise, delegating record management to an operator can let that operator change routing without making it the economic owner of the registration. Inspect the granted authority before using this arrangement.
Wrapped names have additional permission rules
ENS’s Name Wrapper represents wrapped names with ERC-1155 tokens and introduces fuse-based restrictions. For wrapped .eth second-level names, ownership and management are unified differently from the unwrapped registrar arrangement.
Transfers and parent permissions can be constrained until relevant expiry. Check the wrapped state and fuse settings before assuming a generic NFT-transfer flow performs the intended name handover.
Direct answers
Questions people ask
Does changing a resolver transfer the name?
Changing the resolver selects which contract supplies records. Registration ownership and name-control permissions are separate matters.
Is the address receiving payments always the name owner?
No. An address record can point to a different account from the one holding ownership or management authority.
Inspect the evidence
The answer and key facts have stable claim links. These records retain the scope and qualification when reused.
ENS separates the right to a registration, authority to manage a name and the resolver contract that answers record queries. For an unwrapped ENSv1 .eth name, registration ownership and registry management can be separate. Wrapping changes that arrangement. Before transferring a name, check its registrar, wrapped state, controlling accounts and published records rather than assuming all roles are one address.
Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T19:27:58.939Z.
Link to this claimRegistration: The registrar tracks registration ownership and expiry.
Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T19:27:58.939Z.
Link to this claimManagement: The manager can edit records subject to the name’s control rules.
Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T19:27:58.939Z.
Link to this claimResolver: The resolver is a contract serving records, not necessarily the owner.
Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T19:27:58.939Z.
Link to this claimRevision history
- — First publication after primary-source research and separate automated verification.
Source register
Sources and references
Retrieval dates and locators are recorded individually.- ENS terminologyENS Labs
Roles in ENS naming, resolution and management.
Locator: Owner; controller; resolver; registrant · Version / scope: Documentation snapshot retrieved 2 October 2026; response hash recorded separately · Retrieved: 2026-10-02T18:55:25.181ZOpen source - ENS ETH registrarENS Labs
ENSv1 .eth registration and renewal procedure; not an assertion that ENSv2 uses the same pricing or grace period.
Locator: Registering a name; commit-reveal; renewals · Version / scope: ENSv1 registrar documentation · Retrieved: 2026-10-02T18:55:25.210ZOpen source - ENS Name Wrapper overviewENS Labs
Parent control and fuse-based permissions depend on wrapped-name state.
Locator: Wrapped names; subnames; permissions · Version / scope: Documentation snapshot retrieved 2 October 2026; response hash recorded separately · Retrieved: 2026-10-02T18:55:25.327ZOpen source - ENS Name Wrapper expiryENS Labs
Subname rights and burned permissions have expiry conditions.
Locator: Expiry; parent and child names · Version / scope: Documentation snapshot retrieved 2 October 2026; response hash recorded separately · Retrieved: 2026-10-02T18:55:25.302ZOpen source
Research and drafting use AI assistance. A separate automated review checks claims against primary sources; no external expert or named human review is implied. Publication, substantive editing, source retrieval and verification are recorded separately. This version was independently checked by an automated reviewer on 2 October 2026.
Editorial method and correctionsDegrees of Satoshi editorial project. “ENS owner, manager and resolver: who controls which settings?.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/ens-owner-manager-resolver/