Reporch IDE
Connect a custom domain
Add an alias or external FQDN to a completed deployment and verify ownership with the displayed TXT record.
Overview
For a completed deployment or release, you can add an alias prefix under a Reporch-provided address or connect an external domain you own. External domains use an FQDN and the TXT ownership record displayed by Reporch.
Before you start
- Confirm that the target deployment is complete and its default URL works.
- Have permission to change DNS records for the external domain.
- Decide the exact hostname, such as
app.example.com. - Check for existing A, AAAA, CNAME, or TXT records that might conflict at that host.
Steps
1. Select the completed deployment
Open the intended deployment from the dashboard. Check Source and Deployment ID to avoid attaching the domain to another release.
2. Open Custom Domain
Choose the external domain action. If you only need a Reporch-provided address, choose the alias-prefix option instead.
3. Enter the FQDN
Enter only the hostname, such as app.example.com. Do not include https://, a port, /path, or a query string.
4. Add the TXT record
Copy the exact Name/Host and Value displayed by Reporch into your DNS provider. Check whether the provider automatically appends the domain to avoid a duplicated host.
5. Wait for propagation
After saving, wait until the record is publicly resolvable. Before clicking Verify repeatedly, confirm that a public DNS query returns the TXT value.
6. Refresh and verify
Use the status refresh or verification action in Reporch. After verification, open the connected hostname and confirm HTTPS and deployed content.
Input examples
| Input | Result |
|---|---|
app.example.com | Valid FQDN |
example.com | Valid FQDN for an apex domain |
https://app.example.com | Invalid: remove the scheme |
app.example.com/docs | Invalid: remove the path |
Expected result
- The domain state is verified and active.
https://opens without a certificate warning.- Direct access works for important nested routes, not only the home page.
- Content comes from the selected Deployment ID rather than an older release.
Troubleshooting
- Invalid domain/FQDN: Remove scheme, path, and spaces, then verify the complete hostname.
- Verification remains pending: Check public TXT lookup, duplicated Host input, and TTL.
- Reserved domain: Choose another alias or hostname not reserved by Reporch.
- Release not found: Confirm the target deployment still exists and completed.
- Provider integration error: Review the DNS provider connection or use the displayed manual TXT method.
- Another site opens after verification: Check conflicting A, AAAA, or CNAME records and cached DNS responses.