a month ago
I added app.host24.ai as a custom domain and configured both records exactly as shown in the dashboard:
CNAME: app → v2mo4e6f.up.railway.app — verified successfully
TXT: railway-verify.app → railway-verify=6781047f2def613e239094dbe99542 — still shows "Waiting for DNS update"
I confirmed the TXT record is fully propagated and resolving correctly across 20+ global resolvers (checked via whatsmydns.net), so this isn't a DNS configuration issue on my end.
I already tried the standard workaround — deleting and re-adding the custom domain — but it regenerated the exact same verification requirements and the status is unchanged.
This appears consistent with other reports of the same symptom (TXT verification stuck despite propagated DNS). Could you manually clear the verification state for this domain, or let me know if there's anything else to check?
Domain registered today at Namecheap, if that timing is relevant.
1 Replies
a month ago
Two records need updating at your registrar. First, the CNAME is pointing at a target from the previous domain entry (before you deleted and re-added it), so it needs to be changed to the current target shown in your service's Settings under Networking. Second, the TXT verification value that is currently published is truncated and does not match the full token, which is why verification is stuck. Copy the complete value from the dashboard and replace what you have at your registrar, making sure nothing is cut off.
Status changed to Awaiting User Response Railway • about 1 month ago
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