Connecting a root domain or subdomain lets you publish Funnels, Websites, Stores, Blogs, and Webinars using your own branded web address. You can connect supported domains automatically with Domain Connect or configure the required DNS records manually. After connecting the domain, you can assign the correct landing page and configure default and 404/error pages to provide visitors with a consistent experience. This guide covers domain connection, DNS setup, page configuration, removal, and common troubleshooting steps.

What Is a Root Domain or Subdomain?

A root domain is the primary web address for a site, such as example.com. A subdomain adds a prefix to the root domain, such as www.example.com or offers.example.com.

The platform lets you connect root domains and subdomains to supported Sites products so visitors can access Funnels, Websites, Stores, Blogs, and Webinars through a branded URL. Depending on your DNS provider, you can use Domain Connect or configure the required DNS records manually.

Key Benefits of Connecting a Root Domain or Subdomain

Connecting the correct domain gives visitors a branded destination while allowing the platform to route traffic to the appropriate site content.

  • Branded Visitor Experience: Publish site content using a domain or subdomain associated with your business.
  • Flexible Connection Options: Use Domain Connect when supported or configure DNS manually when needed.
  • Automatic SSL: The platform provisions SSL after the domain connects successfully.
  • Controlled Landing Experience: Choose which Funnel step or Website page loads when visitors open the domain without an additional path.
  • Custom Error Handling: Configure a branded 404/error page for visitors who open an unavailable URL.
  • Configuration Reminders: Eligible connected domains can display an Action Required reminder when default-page configuration is incomplete.

Prerequisites and Limitations

Preparing the domain and confirming where its DNS is managed helps prevent connection conflicts and reduces verification delays.

Before you begin:

  • You must own or have access to the root domain or subdomain you want to connect.
  • You need access to the active DNS provider when manual configuration is required.
  • Decide whether visitors should use a root domain such as example.com or a subdomain such as www.example.com or offers.example.com.
  • If the hostname currently supports another website or service that must remain active, use a different available subdomain instead of repointing it.

Current limitations and behaviors:

  • A single hostname cannot point to multiple platforms or servers at the same time.
  • Do not create both an A record and a CNAME record for the same hostname.
  • If Cloudflare manages the DNS, set the applicable A or CNAME record to DNS only, not Proxied.
  • DNS changes may require time to propagate and can take up to 24 hours.
  • The Action Required reminder applies when an eligible connected domain is missing its default page or default 404/error page.
  • The Action Required reminder appears only in the sub-account where the domain was originally connected.

How To Set Up a Root Domain or Subdomain

Connecting the domain in the correct order allows the platform to verify DNS, associate the address with your content, and provision SSL successfully.

Step 1: Decide Whether to Use a Root Domain or Subdomain

Choosing the correct hostname before changing DNS helps prevent an existing website or service from being unintentionally replaced.

A root domain uses the primary address:

example.com

A subdomain adds a prefix:

www.example.com
offers.example.com
go.example.com

Important: If the root domain already hosts another website or service that must remain active, use an available subdomain instead of repointing the root domain.

Step 2: Start the Domain Connection

Starting from the Domains area allows the platform to identify the type of Sites connection and provide the appropriate automatic or manual DNS workflow.

  1. From the Sub-Account view, click Settings.
  2. Select Domains & URL Redirects.
  3. Click + Connect a domain.
  4. Locate Funnel/Website/Store/Blog/Webinar and click Connect.
  5. Enter the root domain or subdomain in the Domain URL field.
  6. Choose the connection method:
    • Continue: Attempt automatic setup with Domain Connect.
    • Add record manually: Configure the required DNS record yourself.
Domain connection screen showing the Domain URL field and connection options

When connecting a root domain, the platform can also add the www version and configure a 301 redirect so traffic from the www address is sent to the root domain.

Step 3: Configure the Domain Automatically or Manually

Use Domain Connect when automatic setup is supported by your DNS provider, or manually add the required DNS record when automatic configuration is unavailable or not preferred.

Automatic Setup with Domain Connect

Domain Connect can authorize a supported DNS provider and automatically create the records required for the connection.

  1. Enter the domain in the connection flow and click Continue.
  2. If the platform recognizes a supported provider, click Authorize.
  3. Sign in to the domain provider when prompted.
  4. Approve the requested DNS connection.
  5. After authorization is complete, close the provider tab and return to the platform.
  6. Allow the platform to verify the DNS configuration.
Domain Connect authorization screen for a supported DNS provider

Manual DNS Setup

Manual setup lets you add the required record directly at the provider that currently manages the domain's DNS.

  1. Enter the domain in the platform and click Add record manually.
  2. Sign in to the provider managing the domain's active DNS.
  3. Add one of the supported records shown below.
Use CaseTypeHost / NameValue / Target
Root domainA@162.159.140.166
SubdomainCNAMESubdomain only, such as www or offerssites.ludicrous.cloud
Supported subdomain alternativeASubdomain only162.159.140.166

Important: Use an A record or CNAME for a supported subdomain configuration, not both for the same hostname. If you use Cloudflare, set the applicable A or CNAME record to DNS only.

Manual DNS configuration showing the required domain record values

Step 4: Associate the Domain With Your Site Content

Associating the verified domain tells the platform which Funnel or Website content should load when visitors use that address.

  1. Wait for the platform to verify the required DNS record.
  2. On the domain association screen, select the applicable Funnel or Website.
  3. Select the Funnel step or Website page that should act as the default landing page.
  4. Click Link Domain.

The platform begins provisioning SSL automatically after the domain is connected. SSL can take a few minutes to complete.

Domain association screen showing the site content selected for the connected domain

Step 5: Configure the Default Page and 404/Error Page

Default-page settings control what visitors see at the main domain and where they are sent when they request an invalid or unavailable URL.

  1. Go to Settings → Domains & URL Redirects.
  2. Locate the connected domain and click Manage.
  3. Review the domain's Connected Products.
  4. If an Action Required reminder appears, click it.
  5. Select an eligible page from the Default Page dropdown.
  6. Select an eligible page from the Default 404/Error Page dropdown.
Connected Products screen showing the Action Required reminder for missing default page settings
Action Required modal showing the Default Page and Default 404 Error Page dropdowns

Note: The Action Required reminder appears only in the sub-account where the domain was originally connected.

You can also manage the default and 404/error page settings through the existing Edit Domain flow:

  1. Go to Settings → Domains & URL Redirects.
  2. Click Manage for the domain.
  3. Open the three-dot menu for the applicable domain or connected product.
  4. Select Edit.
  5. Update the default page or Set default 404/Error Page setting.
  6. Click Save.
Edit Domain modal showing default page and default 404 error page settings

How To Check Your DNS Records

A public DNS lookup can help confirm whether the expected A or CNAME record has propagated before you continue troubleshooting the connection in the platform.

  1. Open a public DNS lookup tool such as MXToolbox.
  2. Select the applicable lookup type, such as a DNS or CNAME lookup.
  3. Enter the root domain or subdomain you connected.
  4. Run the lookup.
  5. Confirm that the expected DNS record is publicly visible.
CNAME: sites.ludicrous.cloud
A record: 162.159.140.166

DNS propagation: Recently changed DNS records may not appear immediately. Allow up to 24 hours before assuming the configuration has failed.

How To Remove a Domain

Removing a domain disconnects it from the sub-account, so confirm that the address is no longer required for active site content before deleting the connection.

  1. Go to Settings → Domains & URL Redirects.
  2. Locate the domain and click Manage.
  3. Open the three-dot menu.
  4. Select Delete.
  5. Confirm the deletion in the confirmation dialog.
Domain management menu showing the Delete option

Troubleshooting Domain Connection Issues

Most connection problems come from records being added at the wrong DNS provider, conflicting records, propagation delays, or Cloudflare proxy settings.

The CNAME or A Record Cannot Be Found

This error means the platform cannot detect the expected DNS record for the hostname being connected.

  1. Confirm which provider hosts the domain's active DNS by checking the nameservers.
  2. Make sure the DNS record was added at that provider.
  3. Check whether the hostname already has an A or CNAME record pointing elsewhere.
  4. Use only one supported record for the hostname:
    • CNAME → sites.ludicrous.cloud
    • A record → 162.159.140.166
  5. Enter only the hostname portion, such as www or offers, in the Host/Name field when required by the provider.
  6. Save the DNS changes and allow time for propagation.
  7. Return to the platform and retry verification.

The Domain Shows an SSL or Privacy Error

SSL cannot complete reliably when the platform cannot verify the hostname or when conflicting DNS records send traffic to different destinations.

  • Remove conflicting A or CNAME records for the hostname.
  • Confirm the required A or CNAME record exists.
  • Review unexpected records that point the hostname to another platform.
  • If you use Cloudflare, make sure the domain connection record is set to DNS only.
  • After correcting DNS, allow time for propagation and SSL provisioning.

A Cloudflare Domain Does Not Connect Correctly

Cloudflare proxying can prevent the platform from validating the A or CNAME record used for Funnels and Websites.

  1. Sign in to Cloudflare.
  2. Open the affected domain and go to DNS.
  3. Locate the A or CNAME record used for the domain connection.
  4. Change Proxy status to DNS only.
  5. Save the change.
  6. Return to the platform and retry the connection after DNS updates.
Cloudflare DNS record with Proxy status configured as DNS only

The Domain Sometimes Shows a 404 Page

Intermittent 404 behavior can occur when different domain versions route inconsistently or when the domain does not have the intended default-page configuration.

  • Check whether visitors are using both the root and www versions of the domain.
  • Configure the appropriate 301 redirect when one version should always send visitors to the other.
  • Confirm that the intended Funnel step or Website page is configured as the default page.
  • Configure a Default 404/Error Page so invalid paths lead to the intended branded error page.

Frequently Asked Questions

Q: Can I add the same domain to more than one sub-account within my agency?
Yes. The platform supports adding the same domain to multiple sub-accounts within the same agency.
Q: How many domains can I add to a sub-account?
The platform does not currently specify a limit on the number of domains that can be added.
Q: Do I need to purchase an SSL certificate separately?
No. The platform automatically provisions SSL after the domain is connected successfully.
Q: Can more than one Funnel or Website use the same domain?
Yes. Multiple Funnels and Websites can use the same domain within the platform. Configure the applicable paths and default-page behavior so each URL routes visitors correctly.
Q: Can I purchase a domain directly through the platform?
Yes. Eligible accounts can purchase and manage domains through the platform's Domain Purchase experience.
Q: Can I manually configure DNS instead of using Domain Connect?
Yes. Manual DNS setup remains available if you prefer to manage the records yourself or your DNS provider does not support automatic Domain Connect.

Need Help?

  • The domain cannot be verified: Confirm the DNS record was added at the provider managing the active nameservers and allow time for propagation.
  • The domain shows an SSL or privacy error: Check for conflicting DNS records and confirm the connected hostname points only to the required destination.
  • You use Cloudflare: Set the applicable A or CNAME record to DNS only instead of Proxied.
  • The domain opens the wrong page: Review the connected product, default page, and URL path configuration.
  • Invalid URLs show an unexpected page: Configure the Default 404/Error Page for the connected domain.