
GoHighLevel Domain & DNS Setup for Funnels (2026)
By Dr Priya Jaganathan, GoHighLevel Certified Admin · HL Growth Partner, Australia · Updated 24 September 2026 · 10 min read
Some links below are affiliate links — if you sign up through them, HL Growth Partner may earn a commission at no extra cost to you. It never changes what we recommend. Full disclosure.
GoHighLevel domain and DNS setup for funnels is a fifteen-minute job that regularly eats an afternoon. The records are simple. What breaks it is everything around them — a stale A record, a proxied Cloudflare entry, a CAA rule nobody remembers adding.
This guide walks the path as we run it for Australian clients: root versus subdomain, the records HighLevel generates, getting SSL to issue, setting a default funnel, and diagnosing the "connected but the page won't load" problem that fills support tickets.
Quick Facts
| Item | Detail |
|---|---|
| Where it lives | Sites > Settings > Domains, then "Connect a Domain" (HighLevel support docs, 2026) |
| Root domain record | A record on @ pointing to the IP HighLevel displays — documented as 162.159.140.166 |
| Subdomain record | CNAME to the target HighLevel generates — documented as sites.ludicrous.cloud |
| SSL | Provisioned automatically once records are correct — no certificate to buy (HighLevel docs, 2026) |
| Propagation | Often minutes; HighLevel and LeadConnector docs allow up to 24–48 hours |
| Redirects | 301 only, from Settings > Domains & URL Redirects, on domains already added to the sub-account |
Why HighLevel domain setup goes wrong for most agencies in 2026
Almost every failed connection we're called into has the same shape: the new record was added correctly, but something older was left in place beside it.
HighLevel's troubleshooting documentation names the usual suspects: multiple A records on one host, leftover AAAA records, CAA records that don't authorise the certificate authority, and domains still attached to another account or product.
The platform is not ambiguous about this — you get one DNS record per host, and mixing an A record with a CNAME on the same name will break it. That single rule explains most of the tickets.
Root domain or subdomain: the choice that decides your whole GoHighLevel domain setup
When the root domain makes sense
Use the root when HighLevel is the whole website — no WordPress, no Squarespace, no brochure site elsewhere. HighLevel's docs note that connecting the root also enables www with a 301 redirect back to it, so you don't manage that pair yourself.
If you're still deciding whether the site belongs in HighLevel at all, start with our comparison of the GoHighLevel website builder versus funnels.
Why agencies default to a subdomain
If the main site lives anywhere else, put funnels on a subdomain — every time. The root's A record is already committed to the existing host, and pointing it at HighLevel takes the client's website offline.
| Option | Record type | Best for | Main risk |
|---|---|---|---|
Root (example.com.au) | A record on @ | HighLevel is the entire site | Overwrites the existing website's A record |
Subdomain (go.example.com.au) | CNAME (A record also supported) | Main site hosted elsewhere | Slightly longer URLs in ads |
www subdomain | CNAME, or auto-handled with root | Migrating an old site wholesale | Conflicts if root is also pointed manually |
The DNS records HighLevel asks for when you connect a domain to GHL
Open Sites > Settings > Domains and choose "Connect a Domain". HighLevel asks which product the domain is for, then generates the records. GoDaddy, Google Domains and Cloudflare can be authorised to write them via Domain Connect; every other registrar is manual.
The values below are what the public documentation shows, but your account screen is the authority — if it displays something different, the screen wins.
| Scenario | Type | Host / Name | Value shown in HighLevel's docs |
|---|---|---|---|
| Root domain to funnel | A | @ | 162.159.140.166 |
| Subdomain to funnel (recommended) | CNAME | go, www, etc. | sites.ludicrous.cloud |
| Subdomain, A record alternative | A | subdomain only | 162.159.140.166 |
| White-label agency portal | CNAME | app | whitelabel.ludicrous.cloud |
| Email sending domain | TXT / CNAME | generated per domain | Unique to your account — never reused |
| IPv6 | AAAA | — | Do not add; documented as a conflict source |
Not on HighLevel yet? Start with a free 30-day trial here — long enough to build everything in this guide before you pay a cent.
SSL provisioning, propagation, and why the padlock still hasn't appeared
HighLevel issues SSL automatically once the domain resolves correctly — there is no certificate to buy and nothing to upload.
When it doesn't issue, the cause is almost always a CAA record. HighLevel's troubleshooting docs state that a conflicting CAA record must be removed, or must authorise pki.goog.
Check CAA before you touch anything else — it is the most common reason a domain verifies but never gets a padlock. Hosts often add CAA records when issuing their own certificates, and those rules outlive the site.
How long to actually wait
HighLevel's root and subdomain guide says to allow up to 24 hours; the LeadConnector troubleshooting article extends that to 24–48 hours while noting most changes update within minutes. VentraIP tells Australian customers the same thing — up to 48 hours for full propagation.
- Lower the record's TTL a day before cutover, as VentraIP recommends, so the old value expires faster
- Test with an external DNS lookup, not your browser, which caches aggressively
- Do the switch outside business hours if email records share the same zone
Read the official record requirements straight from the source in HighLevel's root domain and subdomain setup guide before you raise a ticket.
Setting a default funnel, path routing and redirects without breaking live links
Connecting the domain is only half the job. Until you assign a default funnel or website to it in the Domains screen, visitors hitting the bare go.example.com.au get nothing useful. Everything else routes by path underneath that default.
How paths stack
HighLevel's funnel paths documentation describes three levels: the funnel URL, which always loads step one; the step URL, which loads a specific step; and the page URL, reserved for split testing. Your address is the domain plus the funnel path plus the step path.
Keep paths short and lowercase — /book beats /Book-A-Call-Now-2026 in ad platforms and analytics alike. We still pair every domain build with a pass over slow GoHighLevel funnel pages.
Redirects
Redirects live in Settings > Domains & URL Redirects. HighLevel documents 301 redirects applied to an entire domain or a specific path, and the source domain must already be connected to that sub-account.
Connecting the domain for a white-label agency portal
The agency portal is a separate connection. HighLevel's white-label documentation specifies a CNAME on a subdomain — typically app — pointing to whitelabel.ludicrous.cloud. A root domain can't be used, because CNAMEs aren't valid at the apex.
The same docs note SSL is issued automatically once DNS points at the correct CNAME, with up to 30 minutes for global propagation before provisioning completes. If you're changing an existing white-label domain, delete the old value and save before entering the new one.
Branding, billing and permissions all move together here, which is why we cover the portal domain inside the full GoHighLevel white-label setup.
Australian registrars and the Cloudflare proxy trap
VentraIP, Crazy Domains and GoDaddy AU all manage DNS perfectly well for HighLevel. The friction is in where DNS is actually hosted, which is not always where the domain was bought.
- Check the nameservers first — a Crazy Domains registration may have DNS delegated to Cloudflare, a host, or an old developer's account
- VentraIP customers manage records in VIPcontrol or cPanel depending on the service attached to the domain
- GoDaddy AU accounts can usually use HighLevel's automatic Domain Connect authorisation instead of manual records
- Never delete a record you don't recognise — HighLevel's own guidance warns these often support email or third-party verification
The Cloudflare orange cloud
If the record is proxied, Cloudflare answers with its own IPs and HighLevel's verification cannot see the value it asked for. The same applies to sending records, which is why the Mailgun sending domain setup needs identical treatment.
Set the record to "DNS only" — the grey cloud — for both A and CNAME entries pointing at HighLevel. Cloudflare's own proxy status documentation recommends DNS-only for third-party domain verification and services that aren't compatible with the proxy.
Troubleshooting: "domain connected but the page won't load"
| Symptom | Likely cause | Fix |
|---|---|---|
| Verification fails immediately | Conflicting A or AAAA record on the same host | Delete the extra records; keep exactly one record per host |
| Verified, but no padlock | CAA record blocking issuance | Remove the CAA record or authorise pki.goog |
| Verified, blank or error page | No default funnel or website assigned | Set the default page for the domain in the Domains screen |
| "Domain already connected" | Attached to another sub-account, agency or product | Disconnect at the original location, or use a different subdomain |
| Works for you, not for the client | Local DNS cache or partial propagation | Test via an external lookup tool and wait out the TTL |
| Intermittent or redirect loops | Cloudflare proxy enabled on the record | Switch the record to DNS only |
| Old site still loading | Long TTL on the previous record | Wait out the TTL; lower it before future changes |
If the domain also fronts a WordPress install, routing changes again — see our guide to HighLevel WordPress hosting and integration.
Common mistakes to avoid
- Adding both a CNAME and an A record for the same host, which HighLevel explicitly warns against
- Pointing the root domain at HighLevel while the client's main website still lives elsewhere
- Leaving Cloudflare's proxy on, then blaming HighLevel when verification fails
- Copying record values from another client's account instead of using the ones your screen generated
- Connecting the domain and forgetting to set a default funnel, so the bare URL serves nothing
- Deleting unfamiliar TXT or MX records during cleanup and taking the client's email down too
If you want your domains, funnels and sub-accounts set up properly the first time, book a strategy call with the HL Growth Partner team.
Or if you just need the software first: grab the 30-day HighLevel trial and book us when you're ready to scale it.
Frequently asked questions
Should I use a root domain or a subdomain for GoHighLevel funnels?
Use a subdomain whenever the client's main website is hosted elsewhere, because pointing the root at HighLevel replaces the existing A record and takes that site offline. Use the root only when HighLevel hosts everything. Connecting the root also enables www with a 301 redirect back to it.
What DNS record does HighLevel need for a subdomain?
A CNAME on the subdomain is the recommended method, and HighLevel's documentation shows the target as sites.ludicrous.cloud. An A record pointing to the documented IP is also supported. Always use the exact value your own Domains screen generates rather than copying it from another account.
How long does DNS propagation take for a HighLevel domain?
Most changes resolve within minutes. HighLevel's setup guide allows up to 24 hours and its troubleshooting article extends that to 24–48 hours, matching what Australian registrars such as VentraIP tell customers. If nothing has changed after an hour, treat it as a configuration error, not a waiting problem.
Why is my GoHighLevel domain connected but showing no SSL?
The usual cause is a CAA record that doesn't authorise the certificate authority. HighLevel's troubleshooting documentation says to remove the conflicting CAA record or add pki.goog as an authorised value. SSL provisions automatically once records are correct — there is no certificate to buy or install.
Do I need to turn off the Cloudflare proxy for HighLevel?
Yes. HighLevel's documentation requires A and CNAME records pointing at its infrastructure to be set to "DNS only", shown as the grey cloud in Cloudflare. Cloudflare's own proxy status documentation recommends DNS-only for third-party domain verification and for services that aren't compatible with its proxy.
Can I connect a domain bought from an Australian registrar?
Yes — VentraIP, Crazy Domains and GoDaddy AU all work fine. The important step is confirming where DNS is actually hosted, which is often not the registrar the domain was bought from. GoDaddy accounts can usually use HighLevel's Domain Connect authorisation; most other Australian registrars need records added manually.
How do I redirect an old URL to a new funnel page?
Go to Settings > Domains & URL Redirects and create one. HighLevel documents 301 permanent redirects applying either to an entire domain or a single path, and the source domain must already be connected to that sub-account. Funnels and websites must also be linked to the domain to appear as targets.
Related Articles on HL Growth Partner
Sites, funnels and performance
- Website builder or funnel builder: which to use in 2026
- How to fix slow-loading pages in HighLevel
- Google Tag Manager on GoHighLevel funnels
Email and deliverability
- Setting up Mailgun for HighLevel email
- The GoHighLevel deliverability checklist
- Installing the HighLevel chat widget
