a month ago
This is a follow-up to a previous thread where I was told the CNAME target
had changed and the TXT value appeared truncated:
https://station.railway.com/questions/custom-domain-stuck-on-waiting-for-dns-863b9c72
I updated both records exactly as instructed at 11:50 on 9/4:
- CNAME: qrv.wallace-ig.com.ar → hcpgbqf4.up.railway.app
- TXT: _railway-verify.qrv.wallace-ig.com.ar with the full value
It has now been 5 full days since that update — well past any normal TTL
propagation window (TTL is 14400 seconds / 4 hours). I just re-checked with
dnschecker.org and the CNAME resolves correctly to hcpgbqf4.up.railway.app
globally (only 1 isolated resolver out of dozens didn't resolve, which
doesn't indicate a propagation issue).
The domain is still stuck on "Waiting for DNS update" in Railway's dashboard,
showing the yellow warning icon. Could you please manually force a
re-verification on your end? This no longer appears to be a DNS propagation
issue on my side.
Domain: qrv.wallace-ig.com.ar
Project: zestful-benevolence (prod)
Service: qrv-wallace
1 Replies
Status changed to Awaiting Railway Response Railway • 26 days ago
a month ago
Your DNS records are correct and fully propagated, but the verification workflow stalled before those records were in place, so it never re-ran after you fixed them. We've started a certificate re-issuance for the domain, which should complete verification and issue the TLS certificate within a few minutes.
Status changed to Awaiting User Response sam-a • 26 days ago
19 days 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 • 19 days ago