7 days ago
Custom domain article.ceo has been stuck on "Waiting for DNS update" for over 48 hours.
The required DNS records are publicly resolvable:
CNAME:
article.ceo -> mmyrl1oj.up.railway.app
TXT:
_railway.article.ceo -> railway-verify=cd373ee59fc56847c0afdb3b2eab4c7d4cd4dcd3e457f223e0a4f30dd888132c
The TXT record is successfully resolving through Google Public DNS with NOERROR and TTL 600.
In the Railway dashboard:
- The CNAME record is verified (green check).
- The TXT verification record is still not being recognized.
- The custom domain continues to show "Waiting for DNS update".
The Railway-provided domain is working correctly on port 8080.
Could you please check the domain verification status and refresh/retry the verification and SSL certificate provisioning for article.ceo?
Thank you.
1 Replies
7 days ago
The TXT verification record is published at _railway.article.ceo, but Railway expects it at _railway-verify.article.ceo. The CNAME is correct and propagated, so updating the TXT record's hostname from _railway to _railway-verify at your DNS provider should unblock verification and certificate issuance.
Status changed to Awaiting User Response Railway • 7 days ago
5 hours 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 5 hours ago