a month ago
Custom domain stuck on “Waiting for DNS update” despite valid CNAME and TXT
Custom domain: coordinator.edeeniyat.com
The CNAME is already verified/green in the Railway dashboard and publicly resolves correctly to:
zxlkl5bx.up.railway.app
The required TXT record is also publicly resolving correctly with the exact verification token:
_railway-verify.coordinator.edeeniyat.com
railway-verify=20ffaa64ceaa16bcfcb7f196020fb6638702d54aa24157929450609101962808
We verified the TXT through Google Public DNS (8.8.8.8) and the CNAME through Cloudflare DNS (1.1.1.1).
However, Railway still shows the TXT as pending and the domain remains on “Waiting for DNS update”.
The service itself is healthy and working through the Railway-provided domain.
Could you please re-trigger domain verification / certificate issuance on Railway’s side?
We would prefer not to delete and re-add the custom domain because the DNS records are managed by a third party and are already correctly propagated.
1 Reply
Status changed to Awaiting Railway Response Railway • about 2 months ago
a month ago
Both of your records check out on our side: the CNAME is propagated and the verification TXT matches the expected token exactly. We've re-triggered verification and certificate issuance for the domain, so there's no need to delete and re-add it. It may take a few minutes for the domain to move past "Waiting for DNS update" and for the certificate to issue.
Status changed to Awaiting User Response Railway • about 2 months ago
a month 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 • about 1 month ago