4 hours ago
Hello Railway Support,
My custom domain api.ziclo.in for my production service Ziclo_backend has been stuck on “Waiting for DNS update.”
I have verified the DNS records:
CNAME: api → dtpmyi3u.up.railway.app — publicly resolves correctly.
TXT: _railway-verify.api.ziclo.in — the exact verification token provided by Railway is publicly visible through Google DNS and GoDaddy's authoritative nameserver.
Railway shows the CNAME as verified, but the TXT verification remains pending.
Could you please investigate and manually trigger a fresh DNS ownership verification and reissue the TLS certificate if needed?
Please let me know when it is safe to test the custom domain. I would prefer not to remove or re-add the domain or change the existing DNS records.
Thank you.
1 Replies
Status changed to Awaiting Railway Response Railway • about 2 hours ago
2 hours ago
Both of your DNS records are correct: the CNAME is propagated and the verification TXT record publicly matches the expected token exactly, but the ownership check never re-ran after the record went live.
We've started a fresh verification and certificate issuance for the domain, which may take a few minutes to complete. No changes to your DNS records or the domain entry are needed.
Status changed to Awaiting User Response mykal • about 2 hours ago