Search Atlas Help Center

🌐 Fix White-Label Domain DNS Configuration Issues

Open in
View as Markdown Open in ChatGPT Open in Claude
Camilo Aponte

Camilo Aponte

Last updated on Sep 30, 2026

🔍 Overview

White-labeling allows you to serve the Search Atlas dashboard under your own custom domain (for example, dashboard.youragency.com). If your white-label URL is returning an error page instead of loading the dashboard, the most common cause is an incomplete or incorrect DNS configuration. This article walks you through the correct setup and how to troubleshoot the most frequent issues.

⚙️ Prerequisites

  • Access to your domain registrar or DNS provider (e.g., Cloudflare, GoDaddy, Namecheap).
  • Admin access to your Search Atlas account with Agency settings enabled.
  • The subdomain you want to use (e.g., dashboard.youragency.com).

🛠️ How to Configure Your White-Label Domain

  1. Log in to Search Atlas and go to the apps-grid icon in the header → More Features → Agency Hub (Agency Settings).

  2. Locate the White-Label Domain field and enter your chosen subdomain (e.g., dashboard.dotmappers.in).

  3. Save your settings. Search Atlas will display the DNS record values you need to add at your domain registrar.

  4. Log in to your DNS provider and create a new CNAME record with the following details:

    • Host / Name: The subdomain prefix only (e.g., dashboard).
    • Points to / Value: The CNAME target provided by Search Atlas (copy it exactly).
    • TTL: 3600 (1 hour) or your provider's default.

  5. Save the DNS record at your provider.

  6. Wait for DNS propagation — this typically takes 15 minutes to 48 hours depending on your provider and TTL settings.

✅ How to Verify Your DNS Is Propagating

Before assuming something is broken, confirm that your DNS record has propagated correctly:

  • Visit dnschecker.org or whatsmydns.net and enter your full subdomain (e.g., dashboard.dotmappers.in). Select CNAME as the record type. You should see the Search Atlas CNAME target resolving across multiple locations.
  • If the record is not yet visible, wait and check again in 30–60 minutes.
  • If the record shows a different value, update it in your DNS provider to match the value provided in Search Atlas Agency Settings exactly.

🚨 Common Errors and Fixes

  • Error page / domain not loading: DNS has not yet propagated or the CNAME record is missing. Double-check that you created a CNAME (not an A record) and that the target value matches exactly what Search Atlas provided.
  • SSL / HTTPS warning: SSL certificates are provisioned automatically by Search Atlas after the CNAME propagates. If you see an SSL error shortly after setup, wait up to 30 minutes for the certificate to be issued. Do not add your own SSL certificate.
  • Subdomain resolves but shows a blank or broken page: Confirm the full subdomain entered in Agency Settings matches the subdomain you created in your DNS (including any hyphens, dots, or capitalisation).
  • Cloudflare users — proxy status: If your domain is managed by Cloudflare, make sure the CNAME record is set to DNS only (grey cloud icon), not Proxied (orange cloud). Proxying can interfere with SSL provisioning.
  • Previous A record conflict: If an A record already exists for the same subdomain, delete it before adding the CNAME record. Two conflicting records will prevent the domain from resolving correctly.

📋 DNS Configuration Checklist

  • Record type is CNAME (not A, AAAA, or TXT).
  • Host/Name value is the subdomain prefix only (e.g., dashboard, not the full domain).
  • CNAME target matches the value shown in Search Atlas Agency Settings exactly.
  • No conflicting A record exists for the same subdomain.
  • Cloudflare proxy is disabled (grey cloud) if applicable.
  • Sufficient time has passed for DNS propagation (up to 48 hours).
  • The full subdomain saved in Agency Settings matches what you configured in DNS.

💡 Tips for Faster Troubleshooting

If you need to speed up testing during setup, temporarily lower your TTL to 300 seconds (5 minutes) before making DNS changes. This reduces the time it takes for updates to propagate. Once everything is working, you can raise the TTL back to 3600.

Also, try accessing your white-label URL in an incognito or private browser window to rule out cached DNS responses on your local machine.

🙋 Still Need Help?

If you have followed all the steps above and your white-label domain is still not loading correctly, If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.