Custom domain stuck in VALIDATING_OWNERSHIP 10+ hours despite exact DNS match
makipoint
PROOP

7 days ago

Domain test01.mybizpoint.com stuck in VALIDATING_OWNERSHIP for 10+ hours. Service mybizpoint-app (062a9078-79ff-470e-a7e3-913e9ce7ebd5), project mybizpoint-api (a036effa-0fb5-46ca-aeff-22cf0efc3f93), environment production. Your API reports the DNS record PROPAGATED with currentValue exactly equal to requiredValue (27egn4ce.up.railway.app). CNAME is DNS-only on Cloudflare, TTL 60, no CAA, DNSSEC disabled. Edge routes the hostname on port 80 (301 to https). Staged change applied and redeploy succeeded. customDomainDelete fails with "operation is in progress" so we cannot recycle it. A fresh hostname (prueba.mybizpoint.com) on another healthy service (9301b0e9) also sits in VALIDATING_OWNERSHIP 15+ minutes. Please reset/kick certificate issuance for these domains. We are mid-migration of a production app; this is the last blocker. Thanks!

Awaiting User Response

1 Replies

Railway
BOT

7 days ago

Both domains are missing the required TXT ownership-verification record, which is why they remain in VALIDATING_OWNERSHIP. Custom domains need both a CNAME record and a TXT record before verification and certificate issuance can proceed. For test01.mybizpoint.com, the CNAME also needs updating: it currently points to 27egn4ce.up.railway.app but we now expect oa800ono.up.railway.app. For prueba.mybizpoint.com, the CNAME is correct but the TXT record is also absent. Add the TXT records at the hostnames shown in your service's domain settings in the dashboard (the _railway-verify entries), set them DNS-only in Cloudflare, and once they propagate, verification and certificate issuance will proceed automatically. Reply here once they are in place and we can re-check.


Status changed to Awaiting User Response Railway 7 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...