Skip to content
Custom domain stuck on “Waiting for DNS update”: CNAME verified, TXT not, records resolve publicly
facundoschreiber-commits
OP

a month ago

Custom domain leads.vanillasteel.com (project lead-research, service lead-research-app, environment production) has been on “Waiting for DNS update” for over 5 hours. In the DNS records dialog the CNAME leads → vy1du5cx.up.railway.app already shows as verified, but the TXT _railway-verify.leads does not, although it holds the full 64-character value railway-verify=71c43e3a…c4ad3b745 and resolves on Google (8.8.8.8) and Cloudflare (1.1.1.1). Requests to the domain return 503 “upstream connect error”. Could you re-run or clear the TXT verification? Please keep the same CNAME target if possible, since the DNS is managed by another team.

The TXT value is not truncated: it is the full 64-character token, railway-verify=71c43e3ab65c9ee3f2f8a453e2b01435772d6e34d161dd49fff16e7c4ad3b745, identical to the one in the dashboard. The domain was never deleted or re-added, and the CNAME target is the current one.

Solved

1 Reply

Status changed to Awaiting Railway Response Railway • about 1 month ago


sam-a
EMPLOYEE

a month ago

Your TXT and CNAME records are both correct and resolving publicly, so nothing needs to change on your DNS side and the CNAME target stays the same.

We've re-triggered verification and certificate issuance for the domain. It can take a few minutes to complete, after which the domain will verify and start serving your service instead of the upstream error.


Status changed to Awaiting User Response Railway • about 1 month ago


Railway
BOT

a month 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 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...