Skip to main content

Import a DNS name

Import a DNS domain you own in ENS Explorer: pick onchain or off-chain, turn on DNSSEC, then add one TXT record.

🔧 Known issue: importing a DNS name into ENS isn't working at the moment. We're fixing it. Until then, the steps below won't complete.

Import a DNS domain you own in ENS Explorer: pick onchain or off-chain, turn on DNSSEC and add one TXT record.

Before you start

  • A wallet you control. Your TXT record will contain its address.

  • For an onchain import, a little ETH for network fees (gas).

Important: Whoever controls the domain's DNS settings controls the ENS name. A DNS import is never permanent: the domain's owner can reclaim the name at any time.

Onchain or off-chain?

Route

What you get

Cost

Onchain import

An onchain token for the name. You can edit its records and subnames in ENS Explorer.

One transaction, gas only

Off-chain import

The name works from the TXT record alone. No token, and no profile editing in ENS. It can receive funds at an ETH address, which you change at your DNS provider.

Free

Onchain imports run on ENSv1, the older version of ENS. ENS Explorer says they can be upgraded to ENSv2 in future.

The import screen in ENS Explorer for example.com, with the Onchain import and Off-chain import options and a Begin button

What to set at your DNS provider

Setting

Onchain import

Off-chain import

DNSSEC

On

On

TXT record name

_ens

@

TXT record value

Starts a=, ends with your address

Starts ENS1, ends with your address

Once your wallet is connected, copy the full value from ENS Explorer; it already includes your address. ENS Explorer links to guides for GoDaddy, Namecheap, Dreamhost, Hover and Cloudflare.

The Set up your domain screen in ENS Explorer for example.com, with DNSSEC enabled, the _ens TXT record to add, and Found showing None

Steps

The example.com page in ENS Explorer, saying example.com is available, with an Import name button
  1. Search for your domain in ENS Explorer and open its page. Select Import name.

  2. Choose a route: Onchain import or Off-chain import. Select Begin.

  3. Set up your domain. Select Connect first, so the record shows your address. Then set DNSSEC and the TXT record at your DNS provider, using the table above.

  4. Check. Select Refresh. ENS Explorer shows DNSSEC enabled, and under Found, the address your record points to. When it matches your wallet, there's no warning. DNS changes can take a while: if nothing shows yet, wait and select Refresh again.

  5. Import. Onchain: select Import and approve the transaction in your wallet. Off-chain: there's nothing to send. ENS Explorer finds the record and shows your name resolving to the ETH Address in it.

What can go wrong

  • DNSSEC not enabled: turn it on at your DNS provider, wait, then select Refresh. Still failing? See Why does importing say DNSSEC isn't enabled?

  • Record does not match: the TXT record points to a different address from your connected wallet. Change the record to your address and select Refresh, or connect the wallet it points to. If you import anyway (onchain, Import without ownership), the address in the record becomes the owner, and the name can't be your primary name.


Common questions

Which domains can I import?

Most DNS domains whose ending comes from the ICANN root, such as .com, .xyz or .uk. Domains with letters outside the basic English alphabet can't be imported. Some endings run their own ENS setup instead; the ENS docs list them in Supported TLD List.

Can I import a .ai domain?

Yes, if you can turn on DNSSEC for it. It often isn't available for .ai domains, so ask your registrar first.

Do I buy the domain from ENS?

No. You import a domain you already own and keep renewing it at your registrar. ENS charges no fee; an onchain import costs gas only.

Can I import onchain after an off-chain import?

Yes. Delete the off-chain TXT record (named @, starting ENS1) at your DNS provider, wait for ENS Explorer to pick up the change, then open the name and choose Onchain import. This only goes one way: an onchain import can't go back to off-chain.

Did this answer your question?