How does the ENS App handle name registration and compatibility with existing DNS names?
The ENS APP serves as a platform:
to register .eth names,
import traditional DNS names,
manage ENS names.
This article explains how registration and compatibility with existing DNS names work within ENS.
Overview of ENS
ENS is a decentralized naming system built on the Ethereum blockchain. It allows users to register and manage human-readable names, such as yourname.eth, replacing the need to use complex blockchain addresses.
The ENS protocol is governed by the ENS DAO. The goals and intentions of the ENS DAO are set out in the ENS DAO Constitution which includes Article 4 – ENS integrates with the global namespace
Article 4 – ENS integrates with the global namespace
In order to facilitate making the most widely usable naming system, ENS aims to integrate with the legacy DNS naming system to the greatest extent possible without sacrificing decentralization of ENS. ENS governance will not enact changes that compromise ENS’s ability to do this.
Examples:
Permissible: ENS governance should grant control of a top-level domain to its owner in the DNS system on request.
Not permissible: ENS governance must not create new top-level domains unless those domains have been granted to ENS by a DNS authority.
Supported Names
ENS supports two types of names/domains:
.eth names: Directly registered via the ENS app, these are native to the Ethereum ecosystem and work across chains.
DNS names: Existing DNS names can be imported into ENS, enabling users to manage and configure these names within the ENS platform.
Helpful Information
.eth Name Registration
To register a .eth name, users can use the ENS app and follow this guide: How to Register a .eth name.
DNS Compatibility
Users with existing DNS domain names can import to use these domains as ENS names. To learn more see: Claim your DNS name onchain in ENS
Managing ENS names
Both .eth names and the imported version of the DNS name can be managed in the ENS App. The original DNS remains managed by traditional DNS registrar and hosting service, with the ENS always being tied back to that ownership.