Home/HighLevel/Troubleshooting/Domain not connecting
Troubleshooting · Sites
Fix: GoHighLevel custom domain not connecting. DNS records, exactly.
Domains fail to connect when the DNS records at your registrar do not match what HighLevel asked for, or an old record conflicts with the new one.
The short answer
A custom domain usually fails to connect to GoHighLevel because the DNS records do not match exactly, an old conflicting record remains, the records were added at the wrong DNS host, or propagation has not finished, which can take up to 24 hours, so check each record before changing anything.
Michael is a sponsored HighLevel affiliate. Links to HighLevel use his partner link at no extra cost to you. HighLevel prices and product facts on this page come from HighLevel's own pricing page and help center, checked on the date above.
Causes
Why is a custom domain not connecting to HighLevel?
Most cases come down to the four causes in this table. Check each one before you change anything.
| Cause | How to check |
|---|---|
| Record mismatch | Compare each record character by character |
| Conflicting records | Old A or CNAME records on the same host |
| Wrong DNS host | Where the domain's nameservers point |
| Propagation | Time since the change |
Diagnose
How do you confirm why the domain will not connect before you change any records?
First make sure you are in the right place. HighLevel has three kinds of domain. Site domains for websites, funnels, blogs and webinars are set up in Sites, Settings, Domains. Email sending domains live in Settings, Email Services. The white label app domain lives in Agency Settings, Company, Whitelabel. This page is about the first one. For the others, see DNS records not verifying and white label domain errors.
Then find out where the DNS really lives. The company you bought the domain from is not always the company that hosts its DNS. Look up the nameservers for the domain. Whoever they point to is where records must be added. Records added anywhere else do nothing.
Now compare. Open Sites, Settings, Domains and put the records HighLevel shows next to the records at the DNS host, character by character. A missing dot or an extra space is the usual cause. Look for an older A or CNAME record on the same host name, and note what it does today before you delete it, so you do not take down a live site. Manual changes can take up to 24 hours to spread, so check the time since the last edit before you edit again.
Fix
Fix it step by step.
- Open Sites, Settings, Domains and copy the required records.
- Find where the domain's DNS is actually hosted.
- Delete old records on the same host name.
- Add each record exactly as shown.
- Wait, then verify again.
Still stuck
When to contact support.
If none of these fix it, open Help and Support from the question mark at the top right of your agency view, then start a chat (AI Support Chat or Agent Chat), join a Zoom call or open a ticket. Have your Agency Relationship Number and the Location ID of the subaccount ready, add screenshots of the problem, and turn on Support Access so the team can look inside the account. Only Agency Admins and Agency Users can reach HighLevel support; subaccount users go through their agency.
- Use a subdomain for funnels
- Document every DNS change
If the records match and a day has passed, send support the domain, the DNS provider, a screenshot of the records at the provider, a screenshot of what HighLevel asks for and the time you made the change.
To prevent it, use a subdomain for funnels, keep a note of every DNS change and follow connect a custom domain from the start. Supported providers such as GoDaddy and Cloudflare can connect automatically, which avoids typing records at all. Once the domain verifies, a page that still will not open is covered in fix a funnel page not loading.
Still evaluating? Start with the 30 day GoHighLevel free trial through Michael's link and test this in your own account. Agencies that want the top plan can read about the Founder Plan.

Find where the DNS really lives before you add anything.
Questions
Common questions.
Why is my custom domain not connecting?
A custom domain usually fails to connect to HighLevel because the DNS records do not match exactly, an old conflicting record remains, the records were added at the wrong DNS host, or propagation has not finished, which can take up to 24 hours, so check each record before changing anything.
How do I prevent it?
Use a subdomain for funnels. Document every DNS change.
When should I contact HighLevel support?
Contact support once you have checked every cause on this page and it still fails, or when the fix sits on HighLevel's side. If the records match and a day has passed, send support the domain, the DNS provider, a screenshot of the records at the provider, a screenshot of what HighLevel asks for and the time you made the change.
How long does a custom domain take to connect in HighLevel?
Automatic connections at supported providers are quick. Manual DNS changes can take up to 24 hours to propagate, so wait before you change the records again.
Should I use the root domain or a subdomain?
A subdomain such as go.yourbusiness.com is the safer choice for funnels. It leaves the main website on the root domain untouched.
Why does my domain still show the old website?
An older A or CNAME record on the same host may still point at the old site, or your browser has a cached result. Remove the conflicting record at the DNS host and test in a private window or on mobile data.
Next step
See it in your own account. Thirty days, every feature.
Start a 30 day trial through Michael's link, build the first system and test it before the first invoice. Usage fees for phone, SMS, email and AI can apply during the trial.
HighLevel has three plans at a flat monthly price, each with unlimited users and contacts. See what each one includes and what it costs.
Compare the PlansStarter, Unlimited and Founder