Use your existing .com, .net, or .org domain with cryptocurrency wallets and web3 apps—no new domain purchase required (see Article 4 – ENS integrates with the global namespace). This means it's possible to use, for example, your .com .net or .org DNS name with ENS.
You can enable your DNS name to resolve to Ethereum addresses using two methods, both secured by DNSSEC (the security layer for DNS). This article discusses the offchain method. For information about the onchain method see Claim your DNS name onchain.
Offchain Gasless DNSSEC in ENS
Enable your domain in two steps:
Turn on DNSSEC
Set a unique TXT record
Offchain gasless names require no transactions and no gas fees.
Send zero transactions.
Pay zero gas fees.
Your ENS name works immediately.
Technical information
To address high gas costs, Gasless DNSSEC adopts innovations of ERC-3668 CCIP Read and applies them to accessing names that are not onchain.
CCIP Read fetches and verifies your DNS records during resolution, eliminating the need to submit ownership proof onchain. Documentation can be found on docs.ens.domains
Instructions
You must own the DNS domain you want to enable.
Step 1. Enable DNSSEC on any eligible domain
Some registrars and hosting providers don't support DNSSEC or charge extra for it.
Supported DNSSEC key types
In order for your registrars or hosting providers DNSSEC to work with ENS it must use either RSA/SHA-256 or ECDSA keys.
If they don’t, you’ll need to migrate to a DNS provider that does.
Hosting providers with DNSSEC support
Hosting provider | Key support | Links |
easyDNS | RSA/SHA-256 & ECDSA | |
Google Cloud DNS | RSA/SHA-256 & ECDSA | |
Namecheap | RSA/SHA-256 & ECDSA | |
Hostinger | RSA/SHA-256 & ECDSA |
|
Hostgator | RSA/SHA-256 & ECDSA |
|
Bluehost | RSA/SHA-256 & ECDSA |
|
WordPress does not offer DNSSEC support
If WordPress hosts your DNS, migrate your DNS to another provider. You can continue using WordPress for website hosting.
Step 2. Set the following DNS record
| Type | Name | Value (this format might change) |
Format | TXT | @ | ENS1 dnsname.ens.eth <eth-address> |
Example | TXT | @ | ENS1 dnsname.ens.eth 0xFe89cc7aBB2C4183683ab71653C4cdc9B02D44b7 |
Note for developers or advanced users
DNS Subnames
You can gaslessly resolve DNS subdomains too (of any level, 3LD, 4LD, etc) just by adding the same TXT record for that subdomain.
For
vault.myname.com, instead of name = "@", it would be "vault"For
sub.vault.myname.com, the TXT record name = "sub.vault"
Now anybody would be able to type yourname.com into web3 applications that support ENS, and it would resolve to the provided Ethereum address. Try it here.