Skip to main content
1

Add the domain

Use a subdomain such as go. or links. rather than your apex domain — pointing the apex at a link service takes your website with it.
2

Get the DNS records

Two records: a TXT proving ownership, and a CNAME routing traffic.
3

Create them at your DNS provider

Exactly as returned. A trailing dot, a missing one, or a provider that silently appends your domain to the record name are all enough to fail verification.
Many providers append the zone automatically. If the record name comes back as _dashlink.go.example.com, you may need to enter only _dashlink.go. Check what your provider shows after saving.
4

Verify

DNS propagation takes anywhere from a minute to a few hours. Poll rather than assuming the first attempt will work.
5

Wait for the certificate

Issued automatically after verification, usually within minutes. Links work once this reports issued.

Polling properly

When verification keeps failing

Query a public resolver rather than your own — your network may be caching an older answer.
_dashlink.go.example.com.example.com is the classic symptom of a provider appending the zone to a name you already qualified.
If your DNS provider offers proxying — Cloudflare’s orange cloud — turn it off for this record. A proxied CNAME resolves to the proxy, not to us.
A hostname cannot have a CNAME alongside an A or AAAA record. Remove the others.

File verification

If you cannot change DNS but can publish files:
You then serve a verification file at https://go.example.com/dashlink-verification.txt. You will still need a DNS record to route traffic, so this only helps when the two are managed by different people.