23 days ago
Hi, my custom domain api.ministeriointernacionalaguilasreales.com has been stuck on "Waiting for DNS update" for several days. The CNAME is verified but the TXT row (_railway-verify.api) never passed, even though the DNS is correct and public:
- api.ministeriointernacionalaguilasreales.com resolves to bwihm2vo.up.railway.app (the target Railway shows), confirmed from 8.8.8.8.
- The TXT record _railway-verify.api.ministeriointernacionalaguilasreales.com is published and visible publicly.
It looks like the ownership check was never re-run after the TXT record went live, so the certificate is stuck issuing. Could a team member re-run the verification and re-issue the certificate for this domain? I haven't changed any DNS records.
Thanks.
1 Reply
Status changed to Awaiting Railway Response Railway • 23 days ago
23 days ago
We don't have a stuck verification check here. The TXT record at _railway-verify.api is live, but the value it publishes is shorter than the token we expect. It's cut off partway through, so it doesn't match and the ownership check can't pass.
Copy the full TXT value from the domain's DNS records in the service's Networking settings and replace the published value with it, making sure the whole string is pasted. Your CNAME is already correct and doesn't need to change.
Once the full value is published and has propagated, verification and certificate issuance continue on their own. You don't need to remove and re-add the domain.
Status changed to Awaiting User Response dizzydes90 • 23 days ago
16 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 16 days ago