Good to Know
DNS changes can take 10–30 minutes to propagate — if records are correct, wait and refresh
Your domain must have DNSSEC enabled with RSA/SHA-256 or ECDSA keys to work with ENS
Some TLDs (like .luxe) have custom ENS integrations — the ENS App will show a message if this applies
Switching from offchain to onchain requires removing the old TXT record first, then adding the new one
If the ENS App doesn't detect your DNSSEC, use a DNSSEC Analyzer tool to check for errors
I’ve updated the DNS records, but it’s not proceeding to the next steps.
DNS changes can take time to spread across the internet. If your records are correct, wait 10-30 minutes and refresh the page.
I've set up DNSSEC but the ENS App doesn't detect it
Use a DNSSEC Analyzer tool to look for errors.
I'm not able to use my TLD
Some TLDs like .luxe use their own integration process. If you see a message about custom integration, contact your TLD administrator for instructions.
Switching from offchain to onchain method.
First, remove the TXT record used for the offchain method. Then follow the onchain process: add the new TXT record and import it with a transaction. It may take some time to detect the switch from one TXT record to another.
I see a message saying the TLD has a custom setup
If you see a message like "The team behind [].tld have customised their ENS experience", it means the organisation that operates your domain extension has built their own integration with ENS. This custom setup means:
You can't import the name directly through the ENS App
The TLD operator controls how their domains work with ENS
ENS support can't help with their specific process
What to do: Contact the team behind your TLD directly. They'll be able to explain how their ENS integration works and help you get set up.