Skip to main content

Can I use my DNS domain as an ENS name?

Yes — your .com, .net, or .org can work as an ENS name. Compare the onchain (full features) and offchain (gasless, ETH-only) routes.

Yes. If you already own a .com, .net, or .org, you can set it up so people send crypto to yourname.com, point a decentralised website at it, or use it as your wallet name in any app that reads ENS. You don't move the domain — the setup happens at your DNS provider and, on one route, also in the ENS App.

What you can do with it

Once yourname.com works as an ENS name:

  • People send you crypto to yourname.com instead of a long 0x address.

  • You can point a decentralised website at the name (hosted on IPFS, Arweave, or Swarm).

  • Apps that read ENS see your DNS name in profile views, transaction confirmations, and search results — the same way they'd show a .eth name.

  • Subdomains work too. vault.yourname.com can point at a different wallet from yourname.com.

The full feature set runs on the onchain route. The offchain (gasless) route is more limited — it sets only an ETH address on the name, with no avatar, no other-chain addresses, and no decentralised website. See "Which route should I pick?" below.

Onchain or offchain?

Route

Cost

Where records live

Best if

One gas-only transaction on Ethereum Mainnet

In the ENS App

You want the full ENS feature set — multi-chain addresses, avatar, decentralised website, subnames — and you want to manage records in the ENS App.

Free — no gas, no fee

At your DNS provider

You only need an ETH address on the name (no avatar, no other-chain addresses, no website). You want zero gas. You keep managing in your DNS panel.

Both routes need DNSSEC turned on at your DNS provider. Both let yourname.com work as an ENS name. The difference is where the records live, what you can put on the name, and whether there's a transaction.

Good to know

  • You need to already own the DNS domain at a registrar — ENS doesn't sell DNS domains.

  • Your domain needs DNSSEC enabled using RSA/SHA-256 or ECDSA keys. Most major hosts support it; WordPress.com doesn't.

  • Both routes leave you fully in control of your DNS domain. You don't transfer it anywhere — you just add a record.

  • Subdomains work on both routes. vault.yourname.com can point at a different wallet from yourname.com.

  • For example: Coinbase issues *.cb.id usernames under their cb.id DNS name imported via the onchain route. Over 11 million cb.id usernames have been claimed.

Important: DNS controls ENS. ENS ownership of a DNS name follows DNS ownership. If your DNS domain expires or transfers, your ENS name goes with it. Keep your DNS domain active to keep control.

Which route should I pick?

Most people want onchain. It's the full ENS experience — you can set an avatar, point a decentralised website at the name, add multi-chain addresses, create subnames, and the name behaves like any other ENS name (transferable, manageable in the ENS App).

Pick offchain only if all of these apply:

  • You only need a single ETH address on the name — no avatar, no other-chain addresses, no decentralised website, no text records.

  • You'd rather pay no gas and keep everything in your DNS panel.

  • You're comfortable with the name not appearing in the ENS App as a manageable name.

Offchain → onchain is one-way. You can start offchain and later upgrade to onchain. The reverse isn't practical — once the onchain claim is done, the registration is recorded on Ethereum and takes priority over any offchain TXT record.

What's different about the two TXT records?

Each route adds one TXT record at your DNS provider, but the record format is different:

Route

Name

Value

Onchain

_ens

a=0xYourWalletAddress

Offchain

@ (root)

ENS1 dnsname.ens.eth 0xYourWalletAddress

Don't add both. If you've set one and want to switch routes, delete the existing record before adding the other.

Common questions

Can I switch routes later?

Offchain → onchain works. Delete the offchain ENS1 … TXT record, add the onchain _ens a=… record, then follow the onchain steps. You'll pay one gas-only transaction.

Onchain → offchain doesn't. Once you've done the onchain claim, the name is registered on Ethereum and that registration takes priority. Removing the _ens record and adding an offchain ENS1 … record won't switch resolution back.

Does this work for any DNS domain?

Most DNS domains work — the requirement is DNSSEC with RSA/SHA-256 or ECDSA keys at your registrar. Check your DNS host's docs for "DNSSEC". WordPress.com hosting doesn't support it; move your DNS to another provider if you're hosted there.

Will the ENS name still work if I change my DNS host?

Only if you move the _ens or ENS1 … TXT record and DNSSEC settings to the new host. ENS reads your DNS records — if the records aren't there at the new host, the ENS name stops resolving.

Would a free .eth subname work better for me?

Maybe. If you only want a custom name to receive crypto and don't already own a DNS domain, a free project subname like yourname.uni.eth or yourname.base.eth may fit better — no DNSSEC, no DNS registrar fees, no transaction. See What are project subnames?

What's next?

Did this answer your question?