a month ago
My custom domain www.woningwaarheid.nl has been stuck on "Waiting for DNS update" for several days.
CNAME www → mta59psl.up.railway.app verified (green)
TXT _railway-verify.www.woningwaarheid.nl → railway-verify=e611ab5b2410c12bed7f318447bb7d7dd61f0eba fully propagated worldwide (verified via dnschecker.org)
DNS is correct and propagated globally. Railway still won't verify the TXT record despite clicking the lightning bolt multiple times.
Can you check which exact hostname your system is scanning for the TXT record, and manually trigger verification for service dealcheck-wonen in project powerful-courage?
1 Replies
a month ago
Two issues are preventing verification. First, your CNAME for www.woningwaarheid.nl currently points to nrto3yn4.up.railway.app but our system expects mta59psl.up.railway.app. Second, your TXT record value is truncated - it ends at ...7f318447bb7d7dd61f0eba but the full required token is railway-verify=e611ab5b2410c12bed7f318447bb7d7dd61f0eba685a08530751db13270a7b2e (note the additional 685a08530751db13270a7b2e at the end). Update both records and verification should complete.
a month ago
This thread has been marked as private. Any further activity in this thread will only be visible to you and Railway employees.
Status changed to Awaiting User Response Railway • about 1 month ago
Status changed to Open brody • about 1 month ago
Status changed to Solved brody • about 1 month ago