a month ago
Domain: billing.arkansaslocalroofer.com (project: enthusiastic-healing, service: contractor-billing/web)
Issue: Custom domain stuck on "Waiting for DNS update" for 24+ hours despite DNS records verified correct via external lookups (Google 8.8.8.8) matching exactly what Railway's dashboard requests.
Key symptom: The CNAME verification target has changed three times without me deleting the domain each time: fy85d45v.up.railway.app → fbm2clhr.up.railway.app → 1m6y38se.up.railway.app. The last change happened just from reopening "Show DNS records" on an already-added domain — no delete/re-add involved.
How to reproduce: Re-open "Show DNS records" on an already-added custom domain and the CNAME target changes.
Can someone confirm what the actual stable target should be, or fix the domain verification so it stops rotating?
1 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
The CNAME target for a custom domain is generated once when the domain entry is created and never changes on its own. A different target means the entry was removed and re-added, which draws a fresh random label each time. The TXT verification token works the same way and is reissued along with it. Opening "Show DNS records" is a read-only action and cannot change anything.
Your CNAME currently points at an old target from a previous entry that no longer exists, which is why verification is stuck. The stable target is the one currently shown for that domain in the service's Settings, Networking section - it will stay valid as long as the domain entry is left in place. Update the CNAME at your registrar to match that current value, and verification will proceed.
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