2 months ago
"My custom domain
myclrbook.comhas been stuck on 'Waiting for DNS update' for over 24 hours. The TXT record_railway.myclrbook.comis fully propagated globally (verified on DNSChecker). ALIAS @ →pnnzxvi5.up.railway.appis also resolving. Railway is not picking up the verification. Can someone manually trigger verification from the backend? Project: dependable-nurturing, service: myclrbook."
1 Replies
2 months ago
Your TXT verification record is correctly set up on _railway.myclrbook.com, but our system expects it on _railway-verify.myclrbook.com instead. Additionally, the CNAME/ALIAS for the root domain is not resolving to pnnzxvi5.up.railway.app - it currently resolves to an A record (151.101.2.15), which appears to be a DNS parking page. You'll need to update the TXT record host to _railway-verify and ensure your root domain points to pnnzxvi5.up.railway.app via CNAME or ALIAS record.
Status changed to Awaiting User Response Railway • about 2 months ago
2 months 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 2 months ago