Before you begin
- A Forge project with a workload or static site deployed to a hosted environment, here
prodserving a workload namedapi. Deploy a Go API with managed Postgres gets you there. - Access to the DNS settings of the hostname you are adding.
- Forge v1.6.1 or later (
reliant forge --versioninside the project). Signed in to Reliant,forge cloud domainneeds no separate login.
1
Claim the hostname
--env names the environment whose control plane to talk to; the domain itself is not tied to it:terminal
Output (from a run with guides-sandbox.example.com)
CNAME; an apex gets an A record instead. Claiming does not reserve the name: the first organization to verify it takes it.2
Bind it to a workload
A claimed domain serves nothing until it is bound. For
--target is a workload or frontend name in that environment:terminal
Output
www, add it as a second domain and bind it with --redirect-to app.example.com instead of --target.3
Publish the DNS records
At your DNS provider, create both records exactly as Leave both records in place for good: the TXT token is re-checked on every pass. Do not publish an
domain add printed them, the long TXT token included. domain show prints them again at any time:terminal
Output (trimmed)
AAAA record.4
Verify and wait for HTTPS
The platform re-checks on its own. Once both records resolve, the state moves through ownership checking and certificate issuance to
domain verify checks now and prints what is still missing. This guide’s run used a reserved example.com name with no DNS, so its check failed:terminal
Output (trimmed)
live, usually within minutes of DNS propagating. reliant forge cloud domain ls --env prod shows the state of every domain in the organization. Then curl -I https://app.example.com should answer from your workload. domain verify exits 0 even when the check fails, so read the state: line rather than the exit code.5
Remove a domain you no longer need
unbind stops serving and keeps the verification; rm releases the hostname entirely:terminal
Output
What this does not do
- Domains are not declared in KCL, and a deploy never creates one. A hosted spec that carries a
domainsfield is refused at render. - It does not change your DNS. Reliant cannot speed up your provider’s propagation.
- There is no
AAAArecord and no IPv6 serving today.
Troubleshooting
customdomain: domain does not resolve to the platform
customdomain: domain does not resolve to the platform
The
CNAME (or the apex A record) is missing, misspelled or not propagated yet. Compare what your provider shows with domain show character for character, then run domain verify again.Waiting for DNS for more than an hour
Waiting for DNS for more than an hour
Some providers append your domain to a record name, producing
_reliant-challenge.app.example.com.example.com. Check the saved name. Fix the record and run domain verify; do not remove and re-add the domain, which can run into certificate rate limits.Next steps
Manage production secrets
Give the same environment its own secret values, set from stdin.
Custom domains
Record shapes, every state, conflicts and certificates.
Secrets
The hosted secret store each environment has.
Security model
How Reliant scopes credentials and keeps secrets write-only.