How to Connect a GoDaddy Domain to GoHighLevel Funnels and Websites

GoDaddy’s default DNS settings love to break custom domain setups in GoHighLevel. Between pre-configured parked A records, stale forwarding rules, and mismatched CNAME targets, it’s easy to get stuck waiting hours for an SSL certificate that will never issue.

You don’t need third-party DNS proxies to make this work. If you configure the raw records cleanly, GoDaddy domains hook up to HighLevel funnels and websites with working SSL in minutes. Here’s the exact setup I use across client sites.

The DNS Records GoHighLevel Actually Expects

HighLevel gives you two ways to point traffic to their edge routers: an A record pointing directly to their load balancer IP, or a CNAME record pointing to their hostname routing server. Which one you use depends on whether you’re mapping a root domain (example.com) or a subdomain (www.example.com, offer.example.com).

GoDaddy doesn’t support CNAME flattening on root domains (zone apex). You can’t just point your root (@) to a CNAME like flash.funnels.msgsndr.com. You have to use an A record for the root and a CNAME for subdomains.

Here are the required target values from the GoHighLevel Help Center:

• A Record: Host @ pointing to IP 34.68.234.4 (or 162.159.153.247)
• CNAME Record: Host www (or your custom subdomain) pointing to flash.funnels.msgsndr.com

If you prefer proxying DNS through Cloudflare instead, check our guide on how to connect Cloudflare custom domains to GoHighLevel. If you’re keeping your DNS inside GoDaddy, follow the record setup below.

Step 1: Clean Up GoDaddy Default Parking Records

When you buy a domain on GoDaddy, they automatically insert default DNS records pointing the root apex to their parked sales page (usually an IP like 34.102.136.180). If you leave that parked record in place when adding HighLevel’s IP, DNS queries will round-robin between GoDaddy and HighLevel. When that happens, HighLevel’s Let’s Encrypt validation will fail every time.

1. Log in to your GoDaddy Domain Portfolio.
2. Click your domain name to pull up Domain Settings.
3. Scroll down to Additional Settings and hit Manage DNS.
4. Look through the DNS Records table for any existing A records where Name is @.
5. Click the trash icon on those parked A records and delete them.
6. Check the Forwarding section at the bottom. If domain forwarding is enabled, delete it so it won’t conflict with HighLevel’s routing.

Step 2: Add A and CNAME Records in GoDaddy DNS

Once the zone file is clean, add the official GoHighLevel records. For standard funnels, you almost always want both the root domain (example.com) and the www subdomain (www.example.com) to resolve properly.

In GoDaddy’s DNS Management screen, click Add New Record and add these two entries:

Record 1: The Root Apex (A Record)

• Type: A
• Name: @
• Value: 34.68.234.4
• TTL: 1/2 Hour (or 600 seconds if Custom TTL is available, which speeds up testing)

Record 2: The WWW Subdomain (CNAME Record)

• Type: CNAME
• Name: www
• Value: flash.funnels.msgsndr.com
• TTL: 1/2 Hour

If you’re hooking up a dedicated marketing subdomain instead of your root brand (like go.youragency.com), you don’t need the root A record. Just add a single CNAME record with Name set to go and Value set to flash.funnels.msgsndr.com. We covered this workflow in detail when explaining how to connect a subdomain to a multi-page website in GoHighLevel.

Step 3: Register and Verify the Domain Inside HighLevel

Once the DNS records are saved in GoDaddy, head over to your GoHighLevel sub-account to register the domain.

1. In HighLevel, go to Settings > Domains.
2. Click + Add Domain in the top right.
3. Type your root domain (e.g., example.com) into the input box.
4. HighLevel will prompt: “Add www.example.com as well?”. Click Add both domain and www.
5. Click Add. HighLevel will query DNS servers to verify your GoDaddy records.

If GoDaddy has propagated the records, you’ll see a green checkmark asking which funnel or website to link. If it fails immediately, GoDaddy’s nameservers are still syncing. Give it 2 to 5 minutes and try again.

If you hit an SSL verification loop at this stage, check our guide on fixing GoHighLevel domain SSL pending and DNS errors.

Step 4: Map the Domain to Funnels and Websites

Verifying the domain in your account settings makes it available to use, but visitors will still see a 404 until you actually link it to a specific funnel or website step.

1. Go to Sites > Funnels (or Websites).
2. Open the project you want to publish.
3. Click the Settings tab at the top of the funnel builder.
4. Under the Domain dropdown, select your verified domain (e.g., www.example.com).
5. Choose your Default Page / Step so traffic landing on the bare domain hits your first page.
6. Click Save.

Next, make sure your root domain redirects over to the www version (or vice versa). You can set this under Settings > Domains by editing the root record and picking www.example.com as the redirect target. We broke down the exact redirect behavior in our tutorial on setting up root domain and WWW redirects in GoHighLevel.

Verifying DNS Propagation and SSL Handshakes via Terminal

Instead of clearing browser cookies over and over, use the terminal to see what DNS servers and HighLevel’s edge proxy are actually returning.

Run dig against Google’s public DNS to check the active A and CNAME records:

# Check the root A record
dig @8.8.8.8 example.com A +short # Check the www CNAME record
dig @8.8.8.8 www.example.com CNAME +short

The first query should return 34.68.234.4 with no extra parked IPs. The second query should resolve directly to flash.funnels.msgsndr.com..

To verify that HighLevel has successfully provisioned the SSL certificate and isn’t throwing handshake errors, test it with curl:

curl -ILv https://www.example.com 2>&1 | grep -E "(SSL certificate|HTTP/|Server:)"

A clean HighLevel response will complete the TLS handshake with Let’s Encrypt and return an HTTP/2 200 or HTTP/2 301 status code.

Troubleshooting Common GoDaddy-GHL DNS Conflicts

When a domain refuses to verify or stays stuck on SSL pending, it usually comes down to one of these three gotchas:

1. Conflicting CAA Records

If your GoDaddy DNS zone has a Certificate Authority Authorization (CAA) record restricting issuance to providers like DigiCert or Sectigo, Let’s Encrypt can’t issue your certificate. Check your GoDaddy DNS table for any CAA records. Either remove them or add a CAA record with value 0 issue "letsencrypt.org".

2. Duplicate A Records

GoDaddy frequently leaves old hosting IPs or parked records alongside the new HighLevel A record. If dig example.com A returns more than one IP address, HighLevel’s verification bot will hit the wrong server half the time and drop the connection. Strip out any A record that doesn’t point to 34.68.234.4.

3. Forwarding with Masking Enabled

Never use GoDaddy’s “Domain Forwarding with Masking” to route traffic to a HighLevel preview URL. Masking wraps the entire funnel inside an HTML , which breaks mobile responsiveness, ruins tracking pixels, and drops session cookies.

Frequently Asked Questions

How long does GoDaddy DNS take to propagate to HighLevel?

With TTL set to 1/2 hour (1800s) or 600s, records usually propagate in 5 to 15 minutes. Some local ISPs cache records longer, up to 2 hours. Checking with dig @8.8.8.8 gives you the ground truth.

Can I use one GoDaddy domain for both email sending and funnels?

Yes, but keep the routing separate. Use your root and www (e.g., example.com) for your funnels, and use a dedicated subdomain like mg.example.com or mail.example.com for email. Follow our guide on how to set up a dedicated email sending domain in GoHighLevel to configure MX, SPF, and DKIM without touching your web records.

Why does my funnel show a 404 error after the domain is connected?

This happens when a domain is verified under account settings but hasn’t been assigned under Funnels > Settings > Domain, or the step URL slug is empty. Pick the domain in the funnel settings and verify the step path.

Should I connect my root domain or the www subdomain?

Connect both. Put the A record on @ and the CNAME on www, add both in HighLevel, and set up a redirect from one to the other inside HighLevel so users never land on a dead URL.

Next Steps for Your HighLevel Infrastructure

Once your domain is live with working SSL, make sure you configure URL redirects for legacy campaigns or old backlinks. If you’re migrating an existing site and need to preserve search ranking, follow our walkthrough on how to set up 301 URL redirects in GoHighLevel websites and funnels.