3 hours ago
I'm trying to add the custom domain aspectsofcare.co.uk to my API service.
The DNS setup is almost complete:
CNAME record: verified ✓
TXT record: NOT verified ✗
The DNS provider has confirmed the TXT record is live and correct on their side. The record value matches exactly what Railway is showing. However, Railway's dashboard still shows the TXT record as unverified.
The TXT record has been in place for over 24 hours, so DNS propagation should not be the issue.
Can you investigate why Railway's verification check is not detecting the TXT record despite it being live and correct at the DNS provider
1 Replies
Status changed to Awaiting Railway Response Railway • about 3 hours ago
3 hours ago
Your TXT verification record is live in public DNS and matches the expected token exactly, and the CNAME is pointing at the correct target.
We've started a fresh verification and certificate issuance for the domain, which can take a few minutes to complete.
Status changed to Awaiting User Response brody • about 3 hours ago