18 days ago
My custom domain emesgpt.com has been stuck showing 'waiting for DNS update' in the dashboard for hours, even though I've confirmed DNS has fully propagated (A record resolves correctly to Railway's edge IP, matching my assigned target). Has anyone run into this and found a way to get Railway to re-verify, other than removing and re-adding the domain?
1 Replies
18 days ago
Your traffic-route record is working through Cloudflare, but the ownership verification TXT record is on the wrong host. You have the railway-verify=… value set as a TXT on the root domain (emesgpt.com), but it needs to be at _railway-verify.emesgpt.com. In Cloudflare, add a TXT record with the name _railway-verify and set the value to the full verification string shown in your Railway dashboard under the domain's DNS settings. Once that propagates, verification and certificate issuance should proceed. You can reply here after adding it so we can re-check.
Status changed to Awaiting User Response Railway • 18 days ago
11 days 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 • 11 days ago