2 months ago
I'm trying to connect a custom domain (datumset.app) to my Railway service but it's been stuck on "Waiting for DNS update" for over 24 hours despite DNS being fully propagated globally.
Setup:
- Domain registered on Namecheap, DNS managed by Cloudflare
- CNAME @ → ohp5cfrz.up.railway.app (DNS only, proxy off)
- TXT _railway → railway-verify=fb41cda29b7a8e2e5208eaba2add056fb5f91df6136a15422473b97390606385
- Both records confirmed propagated globally via dnschecker.org
What I've tried:
- Deleted and re-added the custom domain multiple times (each time Railway generates a new CNAME value)
- Tried with Cloudflare proxy ON and OFF
- Tried www.datumset.app instead of root domain
- TXT record is correct and propagated
The service itself is running fine at datum-server-production-a595.up.railway.app
GitHub repo: github.com/pjgiles81-star/datum-server
Note: Every time I delete and re-add the domain in Railway
it generates a new CNAME value, which suggests Railway isn't
finding the TXT verification record.
1 Replies
2 months ago
Your TXT verification record is set on _railway but our system expects it on _railway-verify, so the hostname in Cloudflare needs to be _railway-verify with the same token value. Additionally, the root domain currently resolves to 151.101.2.15 which is not a Railway IP, so you'll want to confirm the CNAME record for @ is pointing to ohp5cfrz.up.railway.app and that there's no conflicting A record in Cloudflare.
Status changed to Awaiting User Response Railway • about 2 months ago
2 months 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 2 months ago