Skip to main content
URLdn verifies your domain with two DNS records: a CNAME record for routing and a TXT record that confirms ownership. Both records must be correct before the domain can become active.

​
CNAME not found

Check that you used the correct host for the domain type:
  • Subdomain such as go.example.com: CNAME host go, value cname.urldn.com.
  • Root domain such as example.com: CNAME host @, value cname.urldn.com.
Some DNS dashboards append the zone name automatically. If yours does, enter only the relative host. Do not enter the entire name twice. For Cloudflare, set the record to DNS only while verification runs. Do not use Proxied mode for the record being verified.

​
TXT not found

Use the exact TXT host and token shown in the URLdn dashboard:
  • Subdomain: _urldn.go
  • Root domain: _urldn
  • Value: urldn-verify=<token>
Some registrars add quotation marks automatically. Do not add your own quotes. If a registrar displays a long TXT value as multiple strings, leave the strings as the registrar stores them.

​
Both records are missing

DNS changes may still be propagating. Wait a few minutes, then choose Verify Now. The button may briefly ask you to wait between checks. URLdn also checks pending domains automatically.

​
Root-domain setup fails

Your DNS provider must support CNAME flattening, ALIAS, or ANAME at the zone apex. If the provider cannot create an apex alias, use a subdomain such as go.example.com or move DNS management to a provider with apex alias support.

​
Token expired

Verification tokens expire after 24 hours. Regenerate the token in the dashboard, replace the old TXT value, and verify again. The old token will no longer match.
You can see whether URLdn found each record in the Verify Now result. If the CNAME is found but the TXT record is not, routing is correct and only the ownership record needs attention.