2 months ago
Hi Railway team,
I'm trying to connect a custom domain to my service but it has been
stuck on "Waiting for DNS update" for several hours despite DNS being
fully propagated.
Project: acceptable-spirit
Service: msp-marketplace
Custom domain: msp.investments
DNS records set in Namecheap:
- CNAME @ → xxxxxxxxxxxx (verified green in your DNS popup)
- TXT _railway →
railway-verify=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
(yellow / not yet verified)
The CNAME is resolving correctly globally (confirmed via
dnschecker.org). The TXT record is set correctly in Namecheap but
Railway has not picked it up yet.
Could you please manually trigger a DNS re-check or advise on what
might be causing the TXT verification to fail?
Thank you,
Arseny
1 Replies
2 months ago
Your CNAME record is correctly propagated, but the TXT verification record is on the wrong hostname. Our system expects it at _railway-verify.msp.investments, but yours is currently set at _railway.msp.investments. Moving the TXT record to use _railway-verify as the host in Namecheap should allow verification and certificate issuance to proceed.
Status changed to Awaiting User Response Railway • 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