Configure Custom Domains

Project domains are connected to a specific lifecycle environment and become available to supported services and public storage routes in that environment.

Add a Domain

1. Open Project settings > Domains.
2. Select the target environment.
3. Choose Namecheap, GoDaddy, or Manual.
4. Enter the root domain and optional subdomain.
5. Follow the provider-specific DNS instructions.
6. Wait for StationOps domain validation to succeed.

Namecheap can import domains after you provide the Namecheap username and API key and allow the required client IP in Namecheap. GoDaddy and manual flows guide you through the DNS changes in the provider account.

Manual DNS Delegation

For a subdomain such as api.example.com, StationOps provides name-server values. Add an NS record for the subdomain label, such as api, using those values in the domain's DNS settings.

For a root domain, follow the displayed delegation instructions carefully because changing authoritative name servers affects every record under the domain.

Validation and Propagation

StationOps checks the domain's validation record and shows whether the connection is active or pending. DNS changes can take time to propagate; the UI notes that full propagation may take up to 48 hours.

Do not attach a pending domain to a production service until validation succeeds and HTTPS works from an external network.

Use the Domain

After the domain is active, select it in a supported service route or storage CDN configuration for the same environment. Deploy the infrastructure change, then verify DNS, TLS, health checks, and application routing.

Keep a Traffic Record Externally Managed

For a custom primary, alternate, assets, or storage CDN hostname, turn off Manage DNS when an existing Route 53 record must remain outside the StationOps CloudFormation stack. StationOps still provisions the hostname's certificate and application ingress, including ACM validation records, but does not create or update its application traffic record.

Generated onstationops.com and preview hostnames are always managed by StationOps. Skip DNS has different behavior: it disables the service's DNS and custom-domain ingress wiring rather than leaving only the traffic record external.