Skip to main content
Live. This area is documented as current, user-reliable behavior.

Goal

Get from owning a domain to routing it where you actually need it.

Prerequisites

  • An existing domain in the portfolio

Workflow

1
Open the domain and inspect DNS controls.
2
Add or review the records required for the target service.
3
Use the project connection surface when the domain is meant for an application deployment.

DNS management behavior

  • Nameservers are editable separately from individual records.
  • The UI distinguishes system-managed records from user-managed records.
  • DNS changes are immediate in the control plane, but propagation still depends on registrar and DNS timing.

Connecting a domain to a project

  • Only active registered domains are available for project attachment.
  • You can attach the apex domain or provide a subdomain like api or www.
  • Primary-domain selection is part of the connection flow.

Expected result

The domain is configured to point at the intended StackShift-managed resource.