1. Overview
  2. Customer Management Portal
  3. Workspace Management
  4. Workspace Custom Domain Management

Workspace Custom Domain Management

Each DashboardFox workspace can be configured with one or more custom domains so that end users access it at a URL you control. This article covers managing custom domains for a workspace from the Customer Management Portal.

Who Can Access Custom Domain Management

Access is restricted to workspace members with the Owner or Member role. Users with the Billing Admin role cannot manage custom domains.

Opening Custom Domains

  1. Go to the main Workspaces dashboard.

  2. Click the action menu on the workspace you want to manage.

  3. Select Custom Domains.

Plan Limits

The number of custom domains a workspace can have depends on its subscription plan. The current usage and limit are shown at the top of the page. If a workspace is at its limit, a domain must be deleted or the plan upgraded before a new one can be added.

If a workspace has more domains than its current plan allows — for example after a plan downgrade — an over-limit banner is shown. No new domains can be added until the count is brought back within the plan limit.

Adding a Custom Domain

  1. Enter the domain in the Domain Name field. Subdomains are recommended (for example, app.yourclient.com).

  2. Click Add Domain.

The domain is registered immediately with a status of Pending DNS. Two CNAME records are generated and shown in the domain row — the workspace owner will need to configure these at their DNS provider.

Note: You cannot add a domain ending in .dashboardfox.app or .yurbi.app. You also cannot add a domain that is already in use by any other workspace in the system.

DNS Records

Expand a domain row to see the two CNAME records required for that domain.

Record 1 — Main Domain Routes traffic from the custom domain to the workspace. The target value is specific to the workspace's server region.

Record 2 — SSL Certificate Delegates the ACME DNS-01 challenge so DashboardFox can issue and automatically renew the SSL certificate. The host for this record begins with _acme-challenge.

Both records must be in place before DNS validation will pass and SSL provisioning will begin. Configuring only the main record will result in the domain remaining in Pending DNS status indefinitely.

Domain Status

Status

Meaning

Pending DNS

Waiting for DNS records to be detected

Active

DNS verified and SSL certificate issued — domain is live

Failed

DNS was never configured and the domain has expired

The system checks pending domains automatically on a progressive schedule — more frequently when a domain is newly added, less frequently as it ages. Once both CNAME records are detected, routing is configured and SSL provisioning begins. SSL is typically issued within 2 minutes of DNS validation passing.

Refreshing Status

Click Refresh Status to pull the latest state from the database. This reflects what the background validation process has most recently written — it does not trigger an immediate DNS check.

Stale Domains

If a domain is added but DNS is never configured, it is automatically marked as Failed after 7 days. The domain name becomes available to be re-added. If you want to use the domain again, delete the failed record and add it fresh.

Deleting a Custom Domain

  1. Click the delete icon on the domain row.

  2. In the confirmation dialog, type DELETE and click Delete Domain.

Deletion removes the domain, its Kubernetes ingress rule, and its SSL certificate. The domain name becomes available to be claimed by any workspace once deletion is processed. This action cannot be undone.

Troubleshooting

The domain has been Pending DNS for an extended period. Ask the workspace owner to verify both CNAME records are configured correctly at their DNS provider. Both the main domain record and the _acme-challenge record must be present. Expanding the domain row shows the exact expected values.

The domain shows Active but users report SSL errors. SSL certificates can take a few minutes to propagate after issuance. If the issue persists beyond 10 minutes, the certificate may not have been issued correctly — delete the domain and re-add it to trigger a fresh provisioning job.

The domain shows Failed immediately after being added. This should not happen under normal circumstances. Failed status is only set after 7 days without DNS configuration, or if SSL provisioning times out after 2 hours following successful DNS validation. If you see it immediately, contact support.

Related Articles

  • Workspace Subscription & Plan Management

  • Audit Logs & GDPR Admin