5 days ago
Hey everyone,
My custom domain tryaudiq.com has been stuck on "Waiting for DNS update"
in Railway for over 5 days despite DNS being fully propagated.
My Railway app works perfectly at the auto-generated URL. CNAME is all
green on dnschecker.org pointing to the correct Railway target. TXT
_railway-verify record is also configured.
Has anyone else run into this? Any fix besides removing and re-adding
the domain (which just generates a new CNAME target)? I'm all out of ideas at this point.
Thanks
Pinned Solution
5 days ago
It may take up to a few hours for Railway to validate the DNS and issue a certificate. (May take up to a day too, but rarely). If it doesn't issue a certificate by then, try removing the domain from Railway and add it back after ~10-15 mins. Update DNS records if necessary.
3 Replies
Status changed to Open Railway • 5 days ago
5 days ago
Your TXT record is malformed. Make sure to click the button to copy what Railway instructed you to add intead of manually selecting the string.
0x5b62656e5d
Your TXT record is malformed. Make sure to click the button to copy what Railway instructed you to add intead of manually selecting the string.
5 days ago
TXT record fixed and all fully propagated per dnschecker.org, but still not verifying. Anything possible for manually triggering verification on the other end?
5 days ago
It may take up to a few hours for Railway to validate the DNS and issue a certificate. (May take up to a day too, but rarely). If it doesn't issue a certificate by then, try removing the domain from Railway and add it back after ~10-15 mins. Update DNS records if necessary.
Status changed to Solved 0x5b62656e5d • 4 days ago