Custom Domains
Pointing your own hostname at a Raklane app, how DNS verification works, and how HTTPS gets issued.
Every App gets a free, working subdomain the moment it's deployed — no setup required. This page is for pointing your own domain (app.yourcompany.com) at it instead.
Adding a domain
From your App's Domains page, add the hostname you want to use (e.g. www.yourcompany.com). It starts out in a pending state.
Pointing DNS at it
Add a DNS record for your hostname pointing at your Raklane installation's ingress address — typically a CNAME (or an A record, if you were given an IP address directly). Ask whoever operates your Raklane installation which one applies, since this depends on how it's deployed.
If you're deploying onto your own server via Bring Your Own Compute, point an A record at that server's own public IP address instead — traffic for a BYOC app goes straight there, not through Raklane's shared infrastructure, and verification checks against that server's IP. If you later move the app between Raklane's compute and a BYOC server (see Where Your App Runs), update the DNS record to match. See Running Apps & Databases on BYOC for the full BYOC walkthrough.
Verification
Raklane periodically checks whether your hostname's DNS actually resolves to the expected address. Once it does, the domain flips from pending to verified — this is what allows Raklane to route traffic to it and issue HTTPS for it. This check runs on an interval, so verification isn't instant; if it's been a while and it's still pending, the Domains page shows a failure reason (e.g. what IP it's actually resolving to right now) to help you tell whether it's a DNS propagation delay or a genuinely wrong record.
HTTPS
Once a domain is verified, Raklane issues a TLS certificate for it automatically the first time a real request for that hostname arrives — nothing to configure. If HTTPS seems stuck, confirm the domain itself has finished DNS verification first; certificate issuance never starts before that.
Removing a domain
Remove it from the App's Domains page at any time. Traffic to that hostname stops being routed to your App as soon as it's removed.
See also
- Troubleshooting — DNS and certificate issues.