3 months ago
I have two custom domains on my Hobby plan that are stuck on "Waiting for DNS update" for over 24 hours. DNS is hosted on Cloudflare with proxy OFF (DNS only). Both CNAME records and TXT verification records resolve correctly (confirmed via dig). The Railway-provided .up.railway.app domains work fine. Edge returns x-railway-fallback: true.
I've tried: switching from Namecheap DNS to Cloudflare, deleting and re-adding domains 3 times, redeploying services, and disabling serverless mode. Nothing changes the status. Is there a known issue with domain verification, or can someone help investigate?
3 Replies
Status changed to Awaiting Railway Response Railway • 3 months ago
3 months ago
x-railway-fallback: true , means railway is receiving the request on the custom domain, but it's falling back to the .up.railway.app origin because the domain verification hasn't completed on their side. In other words: your DNS is routing correctly to Railway's edge, but Railway hasn't "accepted" the domain yet. This is a Railway-side verification state issue, not a DNS propagation issue.
Can you do this:
- Run
dig TXT _railway.yourdomain.comand compare the result character by character to what Railway's dashboard shows - Check Cloudflare DNS for any stale
_acme-challengerecords from prior attempts and delete them - Check if the CNAME record in Railway matches exactly what Cloudflare resolves — run
dig CNAME yourdomain.comand compare to what Railway expects
3 months ago
Have you tried removing all records, waiting for about a day to clear caching/TTL, then readding everything?
2 months ago
Both domains now have valid certificates and are serving traffic. DNS can sometimes take 24-48 hours to fully propagate. Feel free to reopen if needed.
Status changed to Solved jr • 2 months ago