Custom Domains
Attach your own domain names to web services and static sites on Runsite. Each service can have one or more custom domains, all with automatic TLS provisioning via Let’s Encrypt.
Adding a domain
Section titled “Adding a domain”Open the service in the dashboard, go to Custom domains and add the hostname you want to use (for example app.example.com). The dashboard then shows you the exact DNS record to add at your registrar and walks you through verification.
DNS configuration
Section titled “DNS configuration”Point your domain at Runsite using one of these records:
| Use case | Record | Name | Value |
|---|---|---|---|
Root or apex (example.com) | A | example.com | Platform IP (shown in the dashboard) |
Subdomain (app.example.com) | CNAME | app.example.com | <your-service>.runsite.app (web) or <your-site>.runsite.site (static) |
The exact target value is shown in the Custom domain dialog when you add the domain — copy it from there to avoid typos.
Verification
Section titled “Verification”After the DNS records propagate, trigger verification from the same dialog. Runsite checks that the records resolve to the expected target. Once verified, TLS is provisioned automatically — no extra setup needed.
If verification fails, the dashboard shows the expected and actual DNS records so you can fix the mismatch.
Domain status
Section titled “Domain status”| Status | Description |
|---|---|
pending | Domain added, DNS not yet verified. |
verified | DNS verified, TLS provisioning in progress. |
active | Domain fully active with TLS. |
failed | Verification or TLS provisioning failed. |
Removing a domain
Section titled “Removing a domain”Remove a domain from the same Custom domains screen. Traffic to that hostname stops being routed to the service immediately; the certificate is revoked in the background.
Should I use an A record or a CNAME?
Section titled “Should I use an A record or a CNAME?”Use a CNAME for a subdomain like app.example.com, pointing at your service target. Use an A record for a root/apex domain like example.com, pointing at the platform IP shown in the dashboard. Copy the exact value from the Custom domain dialog to avoid typos.
How long does verification take?
Section titled “How long does verification take?”It depends on DNS propagation at your registrar — anywhere from a few minutes to a few hours. Trigger verification after the record has propagated; Runsite checks that it resolves to the expected target.
Do I need to set up TLS myself?
Section titled “Do I need to set up TLS myself?”No. Once DNS verifies, a TLS certificate is issued and renewed automatically via Let’s Encrypt. There’s no manual step on your side.
Why is my domain stuck at pending or verified?
Section titled “Why is my domain stuck at pending or verified?”pending means DNS isn’t verified yet — check the record matches exactly and has propagated. verified means TLS provisioning is still in progress; give the certificate authority time to complete validation before removing and re-adding the domain.
Can one service have more than one custom domain?
Section titled “Can one service have more than one custom domain?”Yes. A web service or static site can serve multiple custom domains, each with its own automatic TLS certificate.