Skip to main content

Import your DNS Domain

Import your .com, .net, .org, or other DNS domain into ENS. Claim your existing domain name onchain with DNSSEC.

Updated yesterday

ENS lets you use your existing .com, .net, or .org domain as a crypto wallet address—for free. This means people can send you crypto at yourcompany.com instead of a long 0x address.

For example: Coinbase *.cb.id usernames are all issued under their cb.id DNS name that was imported into ENS!
Over 11 million cb.id usernames have already been claimed.

Choose between two methods: Onchain (costs gas, proven on Ethereum) or Offchain (gasless). Both work with any DNSSEC-enabled domain.

Onchain DNS Names in ENS

With onchain, you set a text record and submit proof to Ethereum to verify you own the domain. You'll pay Ethereum gas fees to prove ownership and claim your name.


Instructions

You can only claim existing DNS domain names that you own


There are a few pre-requisites to importing a DNS name into ENS

  • The DNS name must have DNSSEC enabled

  • An _ens TXT record must be created on the DNS name containing the wallet address to prove ownership of it.

Go to the ENS App, connect your wallet, search for your DNS domain name and click on it to continue.


1. Enable DNSSEC

Enable DNSSEC first. This security layer proves your domain is legitimate and connects it to ENS. Some providers don't support DNSSEC. Once you've enabled DNSSEC press Check to continue.

Supported DNSSEC key types

Your DNSSEC must use RSA/SHA-256 or ECDSA keys to work with ENS.

If they don’t, you’ll need to migrate to a DNS provider that does.

Hosting providers with DNSSEC support

Hosting provider

Links

easyDNS

Google Cloud DNS

Namecheap

Hostinger

Hostgator

Bluehost

Wordpress does not offer DNSSEC support

If you're using them to host your DNS you will need to migrate to another service for your DNS hosting. (This does not mean you will have to stop using Wordpress)


2. Add the TXT-record

Add a TXT record to your domain to prove you own it. Use your registrar's DNS management panel.

ENS checks for a specific TXT record to confirm you own the domain. This record has the following attributes:

Type

TXT-record

The type of the record you need to create

Name

_ens

The name of the record

Contents

a=wallet address

The content string of the record, a=0x123...
Note that this must be the "checksum" version of the address (the version that has capital letters in it)

TTL

3000

The Time To Live of the record

Create a TXT record with this format: a=walletaddress. Replace 'walletaddress' with your Ethereum wallet address.


3. Claim the DNS name

Return to the ENS App and click Claim and Register to complete the link.


Related Articles


Video Guide


Common Questions

Can I transfer ownership of a DNS-imported ENS name?

Yes, but ENS and DNS ownership are separate:

  • ENS side (wrapped NFT) – You can transfer the wrapped NFT like any other ENS name. This doesn’t affect the underlying DNS ownership.

  • DNS side – Changing DNS ownership doesn’t automatically update ENS ownership. The new DNS owner must update the DNS TXT record and perform a new sync "Refresh DNS" transaction onchain.

Does changing the DNS TXT record automatically update the ENS record?

No. Updating the TXT record doesn’t automatically update ENS.
Anyone can perform a sync "Refresh DNS" transaction at any time to bring the ENS record back in line with the DNS TXT record.

Can I change the manager of an imported DNS name?

Yes. You can set a new manager. However, if you don’t also update the TXT record, anyone could later “sync” the name and revert your changes to match the TXT record.

Do DNS-imported names support Fuses and permissions?

No. Imported DNS names currently can’t use the Name Wrapper fuse system.
Only .eth names support Fuses.

How do I refresh or sync a DNS name in the ENS App?

You can manually trigger a sync using the ‘Refresh DNS’ button in the Ownership tab of your DNS-imported name. This button re-checks your domain’s DNS TXT record and updates the ENS Owner & Manager if there are any changes.

Who can sync "refesh DNS" a DNS-imported name?

Anyone can perform a sync transaction for a DNS-imported name. That’s why it’s important to ensure the DNS TXT record always reflects the correct ownership. If it doesn’t, another user could sync the name back to an outdated or incorrect address.

Did this answer your question?