Connect a custom domain
Serve your knowledge base, status page, verification forms, or game sign-in page from your own hostname.
A custom domain replaces the Enderdash hostname in the links that your players see. You connect one hostname for each product.
Before you begin
You need owner or admin access in the organization. You also need access to the DNS records of your domain. Use a subdomain, because many DNS providers do not allow a CNAME record on a root domain. Wildcards and IP addresses are not accepted.
If Custom domains shows that the feature is not available yet, contact Enderdash support to enable it for your organization.
Choose a hostname for each product that you want to connect:
| Product | Example hostname | What changes |
|---|---|---|
| Knowledge base | help.example.net | The public knowledge base opens at the hostname root. |
| Status page | status.example.net | The public status page opens at the hostname root. |
| Verification forms | verify.example.net | New verification forms use a URL under the hostname. |
| Game OAuth sign-in | login.example.net | The authorization page can open under the hostname. |
Connect the hostname
- Open Custom domains in the organization sidebar.
- Find the card for the product. Enter the hostname in its domain field, such as Public status page domain, and select Connect.
- In your DNS provider, add the CNAME record and the ownership TXT record that the dashboard shows. If Cloudflare manages your DNS, you can select Connect with Cloudflare and approve the records there.
- Select Check DNS. The result tells you which record is missing.
- Wait for the domain to show Connected.
Cloudflare validates the HTTPS certificate automatically after the CNAME record points to Enderdash. This step usually takes a few minutes. Enderdash checks the connection every 15 minutes. To check immediately, select Check connection.
Keep both DNS records after the domain shows Connected.
What each product does with the hostname
The knowledge base and the status page open at the root of the hostname. The publication controls of each product continue to apply. A private status page stays private on your hostname.
New verification forms return a URL under your hostname. Each hostname accepts only the forms of its own organization.
For Game OAuth, the Game OAuth page shows the authorization endpoint of your hostname. Use that endpoint to open the authorization page. Keep the issuer, token endpoint, userinfo endpoint, and signing keys from the Enderdash discovery document. The hostname accepts only the clients and sign-in sessions of its own organization. Account OAuth always uses the Enderdash endpoints.
The original Enderdash links continue to work for every product.
If the domain does not connect
The dashboard shows one status for each hostname:
| Status | Meaning | What to do |
|---|---|---|
| Add DNS records | Enderdash cannot see the CNAME record or the ownership TXT record yet | Compare each record with the dashboard, then select Check DNS |
| Securing connection | Ownership is confirmed and the HTTPS certificate is being issued | Keep the CNAME record in place and wait a few minutes |
| Connected | The hostname serves the product over HTTPS | Keep the DNS records |
| Needs attention | A later check could not confirm the domain. Visitors cannot use it | Restore the records, then select Check connection |
| Removal incomplete | The hostname stopped serving pages, but cleanup did not finish | Select Retry removal |
- If a record is reported as missing, compare its name and value with the dashboard. Then wait for the DNS change to appear.
- If your DNS provider adds your domain to record names automatically, enter only the part before the domain.
- If HTTPS is not ready, make sure that the CNAME record points to Enderdash. Then select Check connection.
Remove a domain
On the Custom domains page, select Remove domain in the product's card and confirm. Its custom links stop immediately. The original Enderdash links continue to work. If you connect the hostname again later, you must add new DNS records.
Next: publish knowledge pages, publish a status page, hosted verification forms, or Game OAuth.
Was this page helpful?
Send a quick note if anything is missing or unclear.
Last updated on