Category

How to Fix a Custom Domain Issues in BoldDesk Using a CNAME Record

Updated:

If a custom domain is not working in BoldDesk, the most common cause is a missing or incorrect CNAME record. BoldDesk requires the custom subdomain to point directly to sslproxy.bolddesk.com.
This article explains how to:

  • Configure the required CNAME record.
  • Map a custom subdomain in BoldDesk.
  • Verify DNS and SSL configuration.
  • Troubleshoot a custom domain that redirects to the default BoldDesk domain.
  • Resolve authentication, attachment, and Cloudflare-related issues.

Common Use Cases

Use this article when:

  • You want to use a custom subdomain for the BoldDesk Customer Portal.
  • The custom domain redirects to the default bolddesk.com domain.
  • The Customer Portal opens through the default domain but not the custom domain.
  • The custom domain was mapped but is not active.
  • Login or authentication fails on the custom domain.
  • Files or attachments cannot be downloaded through the custom domain.
  • An SSL or certificate error appears.
  • The custom domain is reported as blocked.
  • You recently changed or removed a custom domain.
  • You are migrating from the default BoldDesk domain to a custom domain.

How Custom Domains Work in BoldDesk

BoldDesk assigns a default Customer Portal domain to each brand. The default URL follows this format:
https://your-subdomain.bolddesk.com

You can map a custom subdomain, such as:
https://support.yourcompany.com

The custom domain replaces the default BoldDesk domain as the customer-facing portal URL for the selected brand.
To route the custom subdomain to BoldDesk, create a CNAME record that points to:

sslproxy.bolddesk.com

BoldDesk custom domain mapping does not support:

  • Root domains, such as yourcompany.com.
  • Subfolder mapping, such as yourcompany.com/support.
  • A records.
  • ANAME records.
  • URL or domain forwarding.
  • CNAME records pointing to another website or IP address.

Use a subdomain such as support.yourcompany.com or help.yourcompany.com.

Add the CNAME Record

To configure the required DNS record:

  1. Sign in to your DNS provider, such as Cloudflare, GoDaddy, or Namecheap.
  2. Open the DNS management page for your domain.
  3. Create a new record.
  4. Select CNAME as the record type.
  5. Enter the custom subdomain in the Name or Host field.
  6. Enter the following value in the Target, Value, or Points to field: sslproxy.bolddesk.com
  7. Save the record.

Use the following configuration as a reference:

DNS Setting Value
Record type CNAME
Name or Host Your custom subdomain, such as support
Target or Value sslproxy.bolddesk.com
Proxy Status DNS only, when using Cloudflare
  • Do not create an A, ANAME, or URL-forwarding record for the BoldDesk custom domain.
  • Do not point the CNAME to an IP address, website, CDN, or another host.
  • Do not use the root domain.
  • Remove conflicting DNS records that use the same hostname.

DNS providers can display the Name field differently. Some require only the host label, such as support, while others display the complete hostname, such as support.yourcompany.com.

Map the Custom Domain in BoldDesk

After creating the CNAME record:

  1. Go to Agent Portal > Admin > Customer Portal > General.
  2. Select the required brand.
  3. Locate the Custom Domain section.
  4. Click Map Custom Domain.
  5. Enter the custom subdomain.
  6. Click Update.

For complete mapping instructions, explore How to Map a Custom Domain to Your BoldDesk Help Center.

Custom domains are brand-specific. Confirm that the correct brand is selected before mapping or troubleshooting the domain.

Verify the CNAME Record

To verify the public DNS result:

  1. Open MXToolbox CNAME Lookup.
  2. Enter the complete custom subdomain, such as support.yourcompany.com.
  3. Click CNAME Lookup.
  4. Confirm that the result shows:
    • Record type: CNAME

    • Target: sslproxy.bolddesk.com

      MicrosoftTeams-image.png

If the result does not show the expected CNAME target, review the DNS record before continuing.

Incorrect CNAME.png

DNS propagation usually completes within a few minutes or hours but can take up to 72 hours.

Troubleshoot Custom Domain Redirects to the Default Domain

A custom domain can appear to work initially but redirect to the default BoldDesk domain. Use the following procedure to identify the source of the redirect.

Step 1. Confirm the Custom Domain Is Still Mapped

  1. Go to Admin > Customer Portal > General.
  2. Select the applicable brand.
  3. Locate the Custom Domain section.
  4. Confirm that the expected custom domain is displayed.
  5. Confirm that the domain has not been removed or replaced.

If the custom domain was removed, the Customer Portal reverts to the default BoldDesk domain configured for the brand.

BoldDesk does not automatically redirect a removed custom domain to the default domain. If the browser reaches the default domain through the old custom URL, review external redirect, forwarding, proxy, or authentication rules.

Step 2. Confirm the Correct Brand

In a multi-brand organisation, each brand has its own default and custom domain configuration.

Verify that:

  • The correct brand is selected in Customer Portal settings.
  • The custom domain is mapped to the intended brand.
  • The URL being tested belongs to that brand.
  • The default domain displayed for the brand is the expected BoldDesk URL.

A domain mapped to the wrong brand can open an unexpected portal or make troubleshooting results appear inconsistent.

Step 3. Verify the Public CNAME Result

Check the custom hostname using a public CNAME lookup.
The final public result must point to: sslproxy.bolddesk.com

If the lookup returns another target:

  1. Edit the DNS record.
  2. Replace the incorrect target with sslproxy.bolddesk.com.
  3. Remove conflicting A, AAAA, ANAME, CNAME, or forwarding records that use the same hostname.
  4. Save the changes.
  5. Wait for DNS propagation.
  6. Run the lookup again.

A DNS provider’s control panel can show the intended value before the updated record is visible publicly. Verify the public DNS response rather than relying only on the saved DNS configuration.

Step 4. Remove Domain or URL Forwarding

Do not use URL forwarding to send the custom domain to the default BoldDesk domain.
Review the DNS provider and hosting account for:

  • Domain forwarding.
  • URL forwarding.
  • HTTP redirects.
  • Page rules.
  • Redirect rules.
  • Reverse-proxy redirects.
  • Web-server redirects.
  • CDN redirect configurations.

Remove any rule that sends: support.yourcompany.com
to: your-subdomain.bolddesk.com

Step 5. Review Cloudflare Proxy and Redirect Settings

If Cloudflare manages the custom domain:

  1. Open the DNS record.

  2. Confirm that the record type is CNAME.

  3. Confirm that the target is sslproxy.bolddesk.com.

  4. Set Proxy Status to DNS only.

  5. Review Redirect Rules, Page Rules, Bulk Redirects, and Transform Rules.

  6. Remove or disable rules that redirect the custom domain to the default BoldDesk domain.

  7. Review Cloudflare WAF and bot-protection settings.

  8. Allow the updated settings to propagate before testing again.

    Cloudflare.png

A proxied Cloudflare record can apply redirects, caching, WAF challenges, or request transformations before traffic reaches BoldDesk. Use DNS only when validating the custom domain.

Step 6. Test Without Cached Redirects

Browsers can retain permanent redirects and cached portal responses.
To rule out a cached result:

  1. Open a private or incognito browser window.
  2. Enter the custom domain directly.
  3. Test from another browser or device.
  4. Test from another network where possible.
  5. Clear browser cache and site data for both the custom and default domains.
  6. Confirm the final hostname displayed in the browser address bar.

If the custom domain works in a private window but redirects in the normal browser session, clear the cached data and review browser extensions or locally managed policies.

Step 7. Review Authentication Redirect URLs

A custom domain may load correctly and then switch to the default domain during sign-in.
Review the configuration for:

  • OAuth.
  • OpenID Connect.
  • SAML.
  • Social sign-in.
  • Identity-provider callback URLs.
  • Post-login redirect URLs.
  • Sign-out redirect URLs.

Replace references to the default or previous portal domain with the current custom domain where required by the authentication provider.

Before changing authentication settings, keep another supported sign-in method available. An incorrect callback or redirect URL can prevent users from accessing the portal.

Step 8. Review Links and Integrations

The custom domain can appear to redirect when users open a link that was generated using the default or previous domain.
Review:

  • Previously sent ticket emails.
  • Ticket links.
  • File and attachment links.
  • Inline image URLs.
  • Knowledge Base links.
  • Website links.
  • Bookmarks.
  • Email templates.
  • Web forms.
  • Web widgets.
  • API clients.
  • Webhooks.
  • Internal documentation.

Test the Customer Portal by entering the current custom domain manually. If the custom domain remains in the address bar but an old link opens the default domain, update the source of that link.

Step 9. Test a Newly Generated Link

After correcting the mapping:

  1. Open the Customer Portal through the custom domain.
  2. Create or update a test ticket.
  3. Generate a new customer-facing ticket link.
  4. Open the new link in a private browser window.
  5. Confirm that the custom domain remains in the address bar.
  6. Test a newly generated attachment link.
  7. Test sign-in and sign-out.

Previously generated links can continue to contain the old or default domain. Use a newly generated link to test the current configuration.

Step 10. Collect Redirect Evidence

If the redirect continues, collect the following before contacting BoldDesk Support:

  • BoldDesk account URL.
  • Brand name.
  • Default BoldDesk domain.
  • Custom domain.
  • Screenshot of the Custom Domain section.
  • Public CNAME lookup result.
  • Screenshot of the DNS record.
  • Final URL shown after the redirect.
  • Whether the redirect occurs before or after sign-in.
  • Whether the issue occurs in a private browser window.
  • Whether Cloudflare or another CDN or proxy is enabled.
  • Approximate time when the issue was reproduced.
  • Screenshot or recording of the redirect.
    This information helps distinguish BoldDesk mapping behavior from DNS, browser, proxy, authentication, and external redirect issues.

Troubleshoot CNAME Verification Failures

If BoldDesk or the public lookup cannot verify the CNAME, confirm the following:

Check Expected Configuration
Record type CNAME
Hostname The required custom subdomain
Target sslproxy.bolddesk.com
Root domain used No
Conflicting record None
Cloudflare proxy DNS only
DNS propagation Completed

If the DNS provider automatically appends the root domain, enter only the host label. For example, enter support instead of support.yourcompany.com when required by the DNS provider.

Troubleshoot SSL or Certificate Issues

BoldDesk provisions SSL after the CNAME is configured correctly and the custom domain is mapped.
If the browser reports a certificate error:

  1. Confirm that the public CNAME points to sslproxy.bolddesk.com.

  2. Confirm that the domain is mapped to the correct brand in BoldDesk.

  3. Remove conflicting DNS records.

  4. Disable proxying during verification.

  5. Allow DNS propagation to complete.

  6. Review the root domain’s CAA records.

  7. If a CAA restriction exists, allow Let’s Encrypt.

    SSL.png

If a CAA record exists for the root domain, add letsencrypt.org as an authorized certificate authority or remove the restrictive CAA record according to the organization’s DNS policy.

Troubleshoot Cloudflare Authentication Issues

When Cloudflare is enabled, the Customer Portal can load while login requests fail.

Symptoms

  • The portal opens, but users cannot sign in.
  • Ticket pages cannot be accessed after sign-in.
  • Authentication requests return HTTP 403.
  • Browser access works intermittently.
  • Background authentication requests fail.

Cause

Cloudflare features can block or challenge BoldDesk authentication endpoints, including: /account/*
Relevant Cloudflare features include:

  • WAF Rules.
  • Managed Rules.
  • Bot Fight Mode.
  • Super Bot Fight Mode.
  • Browser challenges.
  • Redirect and Transform Rules.

Automated authentication and certificate-validation requests cannot complete interactive Cloudflare challenges.

Resolution

  1. Review Cloudflare security events for the affected hostname.
  2. Identify blocked requests to /account/*.
  3. Create an appropriate Cloudflare WAF Skip Rule for trusted authentication traffic.
  4. Disable challenges for the required authentication endpoints.
  5. Review Bot Fight Mode and Super Bot Fight Mode.
  6. Set the CNAME record to DNS only when validating the configuration.
  7. Wait a few minutes and retest sign-in.

Verify the Result

Test Result Meaning
HTTP 403 through Cloudflare Cloudflare security policies are blocking or challenging the request.
HTTP 200 when Cloudflare is bypassed The BoldDesk authentication service is responding, and the issue is within the Cloudflare configuration.

A browser can complete some Cloudflare challenges, while server-to-server authentication and certificate-validation requests cannot.

Troubleshoot File and Attachment Download Issues

File or attachment downloads can fail when the custom domain uses an unsupported DNS record, URL forwarding, or a proxy that modifies the request.
Confirm that the domain uses:

Record type: CNAME
Target: sslproxy.bolddesk.com

Do not use:

  • A or ANAME records.
  • URL forwarding.
  • A CNAME pointing to another website.
  • A proxy that redirects, challenges, caches, or blocks download requests.

To troubleshoot:

  1. Verify the public CNAME result.
  2. Set Cloudflare Proxy Status to DNS only, if applicable.
  3. Review CDN, firewall, WAF, caching, redirect, and reverse-proxy rules.
  4. Confirm that download requests are not redirected or challenged.
  5. Wait for DNS changes to propagate.
  6. Open the Customer Portal through the custom domain.
  7. Generate a new file or attachment link.
  8. Test the new link in a private browser window.

If the custom or default domain was recently changed, links in previously sent emails can continue to reference the old domain. Test a newly generated link before concluding that the current CNAME is incorrect.

Troubleshoot a Blocked Custom Domain

If BoldDesk reports that the domain is blocked:

  1. Confirm that the domain is a valid subdomain.
  2. Verify that its CNAME points to sslproxy.bolddesk.com.
  3. Confirm that the domain is not mapped to another brand in the account.
  4. Confirm that the domain is not associated with another BoldDesk account.
  5. Check whether the domain is reserved or restricted.

If the CNAME is correct and the issue continues, contact BoldDesk Support and provide:

  • BoldDesk account URL.
  • Custom domain.
  • Selected brand.
  • Screenshot of the blocked-domain message.
  • Public CNAME lookup result.
  • Screenshot of the DNS configuration.

Understand What Happens After Removing a Custom Domain

When an administrator removes a custom domain from a brand:

  • The Customer Portal reverts to the default BoldDesk domain.
  • The removed custom domain no longer provides access to that portal.
  • BoldDesk does not automatically redirect the removed custom domain to the default domain.
  • Bookmarks, website links, email templates, and integrations must be updated.
  • Authentication callback and redirect URLs may require changes.
  • Previously generated ticket and attachment links may no longer work.

For removal instructions, explore How to Remove a Custom Domain from the Customer Portal.

Do not remove a custom domain as a troubleshooting shortcut unless the impact has been reviewed. Removing the domain immediately changes the portal back to its default BoldDesk domain.

Understand Redirect Rules

BoldDesk Redirect Rules apply to Knowledge Base URL paths. They can redirect deleted, invalid, or relocated Knowledge Base links.
Redirect Rules do not replace:

  • Custom domain CNAME mapping.
  • DNS configuration.
  • A domain-level redirect from an old custom domain.
  • Authentication callback configuration.

Use Redirect Rules only for supported Knowledge Base URL redirection within the configured Customer Portal domain.

Troubleshooting Summary

Issue Recommended Check
Custom domain redirects to the default domain Confirm the domain is mapped, verify the brand, check DNS and remove external forwarding or proxy redirects.
Redirect occurs only during login Review OAuth, OpenID Connect, SAML, and other authentication redirect URLs.
Custom domain works in private browsing Clear cached redirects and site data in the affected browser.
Default domain opens but custom domain does not Verify CNAME, mapping status, DNS propagation, SSL, and Cloudflare proxy status.
Portal loads but authentication fails Review Cloudflare WAF and /account/* endpoint handling.
Attachment downloads fail Remove unsupported forwarding or proxy behavior and test a newly generated link.
SSL certificate is not provisioned Verify CNAME, DNS propagation, Cloudflare proxy settings, and CAA records.
Domain is reported as blocked Confirm the domain is not associated with another brand or BoldDesk account, then contact BoldDesk Support.
Old links open the default or previous domain Update bookmarks, templates, websites, integrations, and authentication settings.
Custom domain was removed Use the default domain or remap the custom domain after correcting DNS.

Frequently Asked Questions

  1. Why does my custom domain redirect to the default BoldDesk domain?
    Confirm that the custom domain is still mapped to the correct brand. Then review DNS, URL forwarding, Cloudflare redirect rules, authentication callbacks, cached redirects, and links that still reference the default domain.

  2. Does BoldDesk automatically redirect a removed custom domain to the default domain?
    No. After removal, the portal reverts to the default BoldDesk domain, but BoldDesk does not automatically redirect the removed custom domain.

  3. Why can I not use an A record instead of a CNAME?
    BoldDesk custom domain mapping requires a CNAME record for routing and SSL. A, ANAME, and other record types are not supported.

  4. What should the CNAME record point to?
    The CNAME target must be sslproxy.bolddesk.com.

  5. Can I use my root domain?
    No. Use a subdomain such as support.yourcompany.com or help.yourcompany.com.

  6. Can I map the portal to a subfolder such as yourcompany.com/support?
    No. BoldDesk custom domain mapping supports subdomains, not subfolders.

  7. How long does DNS propagation take?
    DNS changes usually propagate within a few minutes or hours but can take up to 72 hours.

Related Articles

  1. How to Map a Custom Domain to Your BoldDesk Help Center
  2. How to Change a Brand’s Customer Portal Custom Domain in BoldDesk
  3. How to Remove a Custom Domain from the Customer Portal
  4. How to Change the Default Domain in BoldDesk
  5. How to Change or Rename a BoldDesk Subdomain
  6. BoldDesk Redirect Rules: Manage Knowledge Base URL Redirection
Was this article useful?
Like
Dislike
Help us improve this page
Please provide feedback or comments
Comments (0)
Access denied
Access denied
Access denied
Access denied

No articles or sections found
No articles or sections found