My Domain Isn't Validating — Common DNS Issues and Fixes
First: Which Method Are You On?
Open your domain in the dashboard. If LinkHaven asked you to change your nameservers, use the first section. If it gave you DNS records to add (CNAME/TXT — Cloudflare-registered domains and the fallback method), use the second.
Nameserver Method: Stuck on "Pending connection"
1. The Change Didn't Actually Save
Registrars often ask for an extra confirmation (a button, sometimes an email link) after you edit nameservers. Go back to your registrar's nameserver page and confirm both LinkHaven nameservers are showing as the CURRENT values.
2. A Typo, or an Extra Nameserver Left Behind
Both values must match exactly what LinkHaven shows, and there should be no additional nameservers left in the list. Remove any others and re-save.
3. It Just Needs Time
Nameserver changes usually take effect in 5 minutes to 1 hour, but registrars publish them on their own schedule — up to 48 hours is within normal. If your registrar shows the right values and it's been under 48 hours, wait it out; the status flips automatically.
DNS-Records Method: Stuck on "Waiting" or "Failed"
1. A Record Value Has a Typo
Copy-paste, never retype. Open the live panel on your domain card and compare each value character-by-character with your DNS provider.
2. The TXT Record Saved Under the Wrong Name
The SSL records are named like _acme-challenge.yourname.com. Some DNS providers want only the part before your domain in the Name field (enter _acme-challenge); pasting the full name can save it as _acme-challenge.yourname.com.yourname.com — broken. If in doubt, save it both ways and see which one validates.
3. Old Records Are in the Way
If the domain previously pointed at another website, leftover A, AAAA, or CNAME records on the same names block the new ones. Remove the old records for your bare domain and www.
4. On Cloudflare: the Orange Cloud
Set the two CNAME records to DNS only (grey cloud) — click the orange cloud icon to turn it grey, then save. This is the setup we test and support. An orange cloud is not always the cause, though: if switching to grey does not clear the status within an hour, keep working down this list.
5. Your Network Is Caching
LinkHaven checks from our servers, not your device — trust the live panel over what your own browser sees. Caches clear within an hour.
Bare domain stuck, but www works?
If www.yourname.com loads but yourname.com doesn't, check the record at @ at your DNS provider. A bare domain can point at LinkHaven with a DNS record only when your DNS is hosted on Cloudflare. An ALIAS, ANAME or A record at any other DNS provider can't work, and no extra record will fix it. Your domain card shows Action needed when this happens.
There are two ways to fix it:
- Switch to nameservers (recommended). Remove the domain from the landing page, then connect it again with Connect a domain and set the two nameservers LinkHaven gives you. Both yourname.com and www work, with no other records to add. www stops loading until your registrar shows the new nameservers (usually within an hour, up to 48 hours). If you have email on this domain (MX records), contact support before switching so we can carry your email records over.
- Forward the bare domain to www. If your registrar offers URL forwarding, replace the record at @ with a permanent (301) forward from yourname.com to https://www.yourname.com/ (forward only, no masking). Links with a path, like yourname.com/promo, don't carry over, so share the www address. NameSilo's forwarding replaces your www record, so on NameSilo use nameservers.
If your DNS is on Cloudflare, use a CNAME at @ to the value shown in your dashboard, set to DNS only (grey cloud).
When None of This Works
If you're past 24 hours (nameserver: 48) with everything matching, contact support with your domain name and a screenshot of your registrar's settings — we'll find what's blocking it.