Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.ardor.cloud/llms.txt

Use this file to discover all available pages before exploring further.

Custom Domain

​
Overview

Custom domains let you use your own domain names with Ardor services and artifacts. A domain is first connected to a workspace through a DNS challenge. After the domain is verified, Ardor knows that your workspace controls it. From there, you can bind the same verified domain to a service or an artifact inside the platform.
Cerebrum can manage domains and bindings. Just say “add app.example.com to this workspace” or “bind app.example.com to my landing page artifact” — Cerebrum will guide the setup and make the platform-side changes for you.
DNS verification is workspace-level. You do not need to change DNS records every time you move the domain between services or artifacts in Ardor.

​
How Custom Domains Work

The domain lifecycle has two parts:
StepWhat happens
Verify domainAdd the domain in Ardor, create the required DNS records, and verify ownership
Bind domainChoose where the verified domain should route: a service or an artifact
Once the domain is verified, you can rebind it inside Ardor as many times as needed without changing the DNS records.

​
Add and Verify a Domain

1

Create the domain in Ardor

Open the domains interface and create a new custom domain for your workspace.
2

Open DNS records

Click DNS records to see the records Ardor needs for verification.
3

Create records with your DNS provider

Copy the required records into your DNS provider. The exact records depend on the domain and the verification challenge.
4

Verify the domain

Return to Ardor and click Verify. When verification succeeds, the domain is connected to your workspace.
DNS changes may take time to propagate. If verification fails immediately after adding the records, wait a few minutes and try again.
Do not delete the DNS records after verification. Ardor periodically re-verifies domains, and removing the records can cause the domain to lose its verified status.

​
Bind a Domain

After verification, the domain can be bound to a service or an artifact.

Bind to a service

Route the domain to a public service in a specific environment.

Bind to an artifact

Route the domain to a frontend artifact such as a landing page, presentation, or visualization.
You can change the binding inside Ardor whenever you need. For example, the same verified domain can move from one artifact to another, or from an artifact to a service, without changing DNS records.

​
Periodic Reverification

Ardor re-checks domain verification periodically. This protects workspaces from stale or transferred domain ownership. Keep the DNS records active for as long as you want to use the domain with Ardor. If the records are removed or changed, future re-verification may fail.

​
Best Practices

Verification records are not one-time setup records. Leave them in your DNS provider after the domain is verified.
Finish workspace-level verification first, then bind the domain to a service or artifact.
When a service custom domain binding changes, redeploy the environment so routing and system variables are updated at runtime.
After verification, use Ardor to move the domain between platform targets. DNS records only need to stay valid.

​
Troubleshooting

Check that the DNS records exactly match the records shown in Ardor. DNS propagation can take time, so wait a few minutes before trying again.
Make sure the DNS records were not removed or changed. Ardor periodically re-verifies domains.
Redeploy the service environment after saving the domain binding. The redeploy updates runtime configuration and system variables.
Change the binding inside Ardor. If the domain remains verified, you do not need to change DNS records.

​
What’s Next

Networking

Learn how services expose public URLs and custom domains

Artifacts

Create frontend artifacts for landing pages, presentations, and visualizations