Setup and operations
Connecting a Custom Domain to a DuckRoute Flow
Domain setup succeeds when the hostname resolves predictably, reaches the intended flow, and has a documented rollback path.
Inventory the hostname before editing
Record registrar, DNS provider, current records, TTL, certificate handling, existing traffic, and the flow owner. Check whether email, verification, or another service depends on neighboring records.
Create an exact host mapping
Choose the public scheme, hostname, and optional path behavior, then map them to one intended flow. Avoid ambiguous duplicate hosts across active configurations because matching becomes harder to reason about.
Change DNS deliberately
Add the documented record value, allow for propagation, and verify resolution from more than one network. Keep the former value and change time so rollback does not depend on memory during an incident.
Validate both page paths
Check White Page and Target Page health directly, then through the public hostname with representative request fixtures. Include TLS errors, bad upstreams, and unknown paths in the test plan.
Approve the complete public route
Confirm DNS, certificate, host selection, event attribution, response delivery, canonical campaign URL, and fallback behavior. Transfer the hostname into the domain inventory only after another operator can repeat those checks.