2 months ago
project c795ebfa-3486-412a-96db-8055a15c6ef1
The domain has been correctly pointed to Railway for over 72 hours and still shows “Waiting for DNS update” in the dashboard.
Current DNS state (verified from multiple resolvers):
• A record for → 76.76.21.21
• Verified via GoDaddy, Google (8.8.8.8), and Cloudflare (1.1.1.1)
• dig consistently resolves correctly
• TTL is 600 seconds
The Railway app itself is running and accessible via the Railway-provided URL, so deployment is healthy.
Given the above, it appears the DNS is fully propagated and this may be a domain verification / cache issue on Railway’s side.
Can Railway re-trigger domain verification, or manually refresh the domain status on your end?
Thanks a lot for the help!
1 Replies
2 months ago
You need to add a CNAME record provided by Railway when adding your custom domain. You should not be adding A records.
Additionally, if you're using your root domain, you should be adding both @ and www DNS records.
I would suggest using Cloudflare's DNS to minimize any possible issues, such as the one where certain providers don't support CNAME flattening.