Troubleshoot custom domains, DNS, and certificates

Verify from the inside out

1. Confirm the current deployment is healthy on its BlinkHost hostname.
2. Compare the dashboard's required DNS name and value with the authoritative DNS response.
3. Check ownership verification, routing status, and certificate status separately.
4. Test HTTPS using the exact hostname after the dashboard reports readiness.

DNS TTLs and cached resolvers can delay observation. Repeatedly deleting and recreating records or the BlinkHost domain resource resets evidence and can extend the outage. Keep an existing healthy production route until the replacement is verified. Escalate with the hostname, expected record type, observed public answer, certificate state, and UTC time—never registrar credentials or private keys.