24 days ago
Hello Railway team,
My custom domain beta.galachefs.com has been stuck on "Waiting for DNS update" for several hours (6+ at this point).
The required CNAME (beta → ifi0vafj.up.railway.app) and Railway verification TXT record (_railway-verify.beta) are now correctly configured and publicly resolving. I have confirmed both directly against my domain's authoritative nameservers (Namecheap), not just cached public resolvers.
The Railway-generated domain (remy-production-295a.up.railway.app) works correctly and the service is healthy on port 8080.
I found several recent solved threads with the same symptoms, where Railway confirmed that the domain verification/certificate workflow had stalled and restarted the certificate issuance process.
Could someone from Railway please check whether the verification or certificate workflow for this custom domain is stuck and trigger a re-verification or certificate re-issue if required?
I would prefer not to delete and recreate the domain because the required DNS records are already correctly configured and propagated.
thank you
1 Replies
24 days ago
Your CNAME is correctly propagated, but the TXT verification record at _railway-verify.beta has a truncated value: it ends with ...3b90d while the expected token ends with ...3b90db (the final b is missing). Update the TXT record value at your registrar to match the full token shown on the domain's settings page in the dashboard, and verification and certificate issuance will resume automatically once it propagates.
Status changed to Awaiting User Response Railway • 24 days ago
Status changed to Solved megsgrace-chef • 24 days ago