Tasks
Custom domains
Serve a published app from your own address — add the domain, copy the two DNS records, verify, and Dhanu issues the HTTPS certificate for you.
A published app lives at your-app.apps.dhanu.ai by default. If it is
customer-facing, you probably want it at an address of your own —
tools.yourcompany.com, say. That is the Domains tab in the app’s settings.
You can add up to three domains to one app.
How it works
-
Add the domain. Type it without
https://—app.yourdomain.com. It has to be a domain you control; addresses on the Dhanu apps domain are rejected. -
Add two DNS records at whoever runs your DNS. Both are shown with a copy button beside each value:
Type Host Value CNAME your domain The target Dhanu gives you TXT _dhanu-verify.your-domainThe verification string Dhanu gives you -
Press Verify. Dhanu looks up both records. The TXT record proves the domain is yours; the CNAME is what actually routes traffic.
What the status means
| Status | What is happening |
|---|---|
| Pending verification | The records are not visible yet — DNS changes can take minutes to hours to spread |
| Verifying | Dhanu is checking |
| Active | The domain is serving your app over HTTPS |
| Action needed | Verification failed — usually a typo in a record, or one of the two missing |
HTTPS certificates are issued and renewed automatically once a domain is active. There is nothing to buy, upload or remember.
Removing one
Delete the domain from the list and it stops serving the app. Your
.apps.dhanu.ai address keeps working, so the app never goes dark while you
move things around.
Working with it well
Use a subdomain, not the root. app.yourcompany.com is a CNAME away;
pointing an entire root domain at an app is a bigger decision and some DNS
providers cannot do it cleanly.
Verify after the records have spread. If it fails, wait and try again before assuming the records are wrong — the check is cheap and repeatable.
Publish first. A domain only means something once there is a live release behind it.