12 days ago
I'm trying to connect the custom domain asktheunknown.com to my service. The CNAME record verified successfully within a few hours and is showing green/active. However, the required TXT verification record (_railway-verify) has had the correct, complete value in DNS for over 24 hours, confirmed via dnschecker.org showing it propagated globally, and double-checked directly in my registrar's (Namecheap) DNS panel — yet Railway's dashboard still shows "Waiting for DNS update" for the domain.
I've also confirmed there's no conflicting record and no CAA record blocking certificate issuance. Could someone manually re-trigger verification for this domain, or help identify what's actually blocking it on your end?
TXT record value: railway-verify=4f637de736d4aadb3f3fe109efa1f726169f8fabfdf6fc0e7456683b3b80c01e
Pinned Solution
12 days ago
It may take up to a few hours (maybe even a day) for Railway to validate the DNS and issue certificates. If one isn't issued by then, try removing the domain from Railway and add it back after ~10-15 mins. Update DNS records as necessary.
2 Replies
12 days ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 12 days ago
12 days ago
It may take up to a few hours (maybe even a day) for Railway to validate the DNS and issue certificates. If one isn't issued by then, try removing the domain from Railway and add it back after ~10-15 mins. Update DNS records as necessary.
0x5b62656e5d
It may take up to a few hours (maybe even a day) for Railway to validate the DNS and issue certificates. If one isn't issued by then, try removing the domain from Railway and add it back after ~10-15 mins. Update DNS records as necessary.
11 days ago
Thank you. I removed it (at Railway -settings-network) and then replaced it. Within 10 seconds it showed the green check mark (successful). I actually didn't wait the allotted time of 10-15 minutes and it went surprisingly well. Such a simple solution to what I have used too much time thinking about. Thanks again.
Status changed to Solved 0x5b62656e5d • 11 days ago