2 days ago
Service: bubbly-bravery (project outstanding-joy).
Custom domain www.squadlinkapp.com has been stuck on "Waiting for DNS update" in Settings > Networking for over an hour, and no SSL certificate has been issued (browsers show a certificate/privacy error).
The required records shown in Railway's "Configure DNS Records" modal are correctly set on our DNS (OVH):
- CNAME www -> qert3274.up.railway.app
-
- TXT _railway-verify.www -> railway-verify=1e9de0c03f3c5e2ab4eff0e8cd26e8665c4d588a62d22273a7f6e870e39c0ba8
Both are fully propagated globally (checked via dnschecker.org) and I also confirmed the TXT via a direct authoritative query to Google's public DNS (dns.google), which returns the exact expected value directly from OVH's nameserver.
In the "Configure DNS Records" modal, the CNAME shows as valid (green check) but the TXT still shows as not valid (warning icon), even though DNS is confirmably correct and propagated.
I found a similar solved thread here (custom-domain-stuck-on-waiting-for-dns-c73a980b) where the fix was adding the _railway-verify TXT record - I've already done that, but the domain is still stuck. Could you please manually trigger a re-verification / certificate issuance for this domain?
Thanks for your help!
1 Replies
2 days ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 2 days ago
2 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.