Custom Domain DNS and Bind Troubleshooting

Where you see this in the app

This guidance applies to Settings → Custom domains, especially once a hostname has already been saved and the page is showing DNS instructions or a status badge.

The two required DNS records

The page tells the user to add two DNS records before binding:

If either one is missing or incorrect, the setup may stall at a pending state.

Status labels and what they usually mean

The status badge is the first troubleshooting clue.

DNS pending does not necessarily mean the feature is broken. It often just means the DNS records are not visible yet to the system.

Bind step and common failures

Bind is the step that tells the platform to verify DNS and issue managed TLS.

Common reasons the bind step does not advance are:

• the CNAME points to the wrong destination,
• the TXT value does not match exactly,
• DNS propagation is incomplete,
• the user is trying too early after adding records,
• the hostname is not the expected subdomain shape.

The page itself warns users to add the records first, wait for propagation, and then click Bind.

What to check before retrying

Before trying Bind again, the user should verify:

1. the hostname is a subdomain they control,
2. the CNAME target matches the page instructions,
3. the TXT record name and value match exactly,
4. enough time has passed for propagation,
5. the page is not showing Bound (TLS ready) already.

If the page shows DNS verified, the safest action is usually patience rather than changing the records again immediately.