How to Fix DNS Errors When Your Custom Domain Will Not Connect
If your custom domain will not connect, the fix is almost always a wrong or missing DNS record at your domain registrar — not a problem with your funnel builder. Check your CNAME and A records first.
Common DNS Errors and What They Actually Mean
DNS errors sound scarier than they are. Most come down to one of a handful of causes.
- DNS_PROBE_FINISHED_NXDOMAIN: the domain cannot be found at all, usually a typo or a record that was never saved.
- SSL Certificate Error: the domain resolves but the security certificate has not finished issuing yet.
- Too Many Redirects: conflicting records are sending traffic in a loop.
- Domain Verification Pending: the platform has not detected your DNS change yet, even though you made it correctly.
Knowing which error you are looking at tells you
where to look next.
How to Check Your Domain's Current DNS Records
Before changing anything, look at what is actually set right now.
Log in to your domain registrar — this is wherever you bought the domain, like GoDaddy or Namecheap, not your funnel builder. Find the section usually called DNS Management or DNS Settings.
- A Record: points your root domain (example.com) to an IP address.
- CNAME Record: points a subdomain (like www) to another domain name.
- TXT Record: often used to verify you own the domain.
- Nameservers: control which company manages your DNS in the first place.
Compare what you see against the exact values your platform gave you when you added the domain.
How to Fix a CNAME Record Error
This is the most common mistake. People type the target value with a trailing dot, an extra "www," or a typo in the middle.
Delete the existing CNAME record entirely rather than editing it. Then add a fresh one, copying the target value character by character from your platform's instructions.
- Host/Name field: usually just "www" — do not include your domain name here.
- Target/Value field: paste exactly what your platform gave you, with no extra spaces.
- TTL (Time to Live): leave on the default unless told otherwise.
Save the record, then move on to checking your A record.
How to Fix an A Record Error
The A record handles your root domain — the version without "www" in front. If people typing just "example.com" get an error, this is usually why.
Check that the A record's value is the exact IP address your platform provided, not a placeholder or an old value from a previous host.
- Duplicate A Records: having two A records for the same host confuses browsers. Delete the old one.
- Wrong IP Address: copy-paste it rather than retyping to avoid a single digit mistake.
- Missing Root Record: some registrars use "@" instead of a blank field for the root domain — check both.
One correct A record is enough. Two conflicting ones is the more common problem.
How Long DNS Changes Actually Take to Propagate
DNS propagation is the delay between saving a record and the whole internet recognizing it. It is not instant, and that is normal.
- 15 Minutes to 1 Hour: the most common wait time with modern registrars.
- Up to 24 Hours: possible if your registrar has a longer default TTL.
- Up to 48 Hours: rare, but can happen after a recent nameserver change.
If it has been under an hour, the fix is usually just to wait and refresh. If it has been over 24 hours, something in the record itself is wrong.
When the Problem Is Not DNS at All
Sometimes every record is correct and the domain still will not connect. This is the part most guides skip.
Check whether your domain was previously connected somewhere else, like an old WordPress host. Leftover records from a past provider can sit alongside your new ones and cause a conflict, even though nothing looks obviously wrong.
- Old Hosting Records: search your DNS list for any A or CNAME record you do not recognize and delete it.
- Domain Lock: some registrars lock a domain against changes by default — check for a lock or transfer-protection toggle.
- Cached Browser Data: your own browser may show an old error even after the fix works. Try a different browser or your phone's data connection to confirm.
Ruling out these three covers almost every case that survives a correct DNS setup.
Getting DNS right is a one-time job — once your domain connects, it stays connected. From here, you're in a good position to build your first sales funnel free on that domain.

Comments
Post a Comment