a day ago
Project: creatoros (environment: production)
Two custom domains have been stuck in "Validating domain ownership" for over an hour. DNS is correct and resolves globally (Route 53; checked on the authoritative servers and on 8.8.8.8 / 1.1.1.1 / 9.9.9.9):
service api
api.aiinspirelabs.com CNAME st67o4l0.up.railway.app
_railway-verify.api TXT "railway-verify=c341a688f9c99936d9aa4ad18fc095190d6d6a6bc96ea9a2a173826289c5ac1c"
service app
app.aiinspirelabs.com CNAME 77p7o8ot.up.railway.app
_railway-verify.app TXT "railway-verify=ebf40947f37f8c204bf6a405c14ce69a6075753ffb644e439f3bdf9ffc71304d"
The edge already routes both hosts to the services (HTTP 200 when ignoring the certificate), but it still serves the generic *.up.railway.app certificate. No CAA records, no DNSSEC, no proxy. The domain's name servers were misconfigured at first and were fixed ~2 hours ago; both domains were removed and re-added after that.
Could you re-trigger the verification and issue the certificates for both domains? Thank you!
1 Replies
a day ago
Both domains have passed ownership verification and their CNAME records match what we expect. The certificate step is what's still pending: when our certificate check last tried to reach both hostnames over HTTP, the request didn't complete.
Since your nameservers changed only a couple of hours ago, the most likely reason is that some DNS resolvers still have the old answers cached, even though your authoritative records are now correct. You don't need to change any records, and you don't need to remove and re-add the domains again. Doing that would generate new CNAME targets and verification tokens. Your DNS is already in place, so the certificates should be issued once that check can reach the hostnames.
Status changed to Awaiting User Response Railway • 1 day ago