2 months ago
Hi team,
Custom domain payments.fiveam.music (CNAME target tbqoz76n.up.railway.app, port 8080) is stuck in "Waiting for DNS update." The dashboard shows the CNAME verified (green) but the _railway-verify.payments TXT still flagged as pending.
The TXT record is live and globally propagated — it returns the exact expected value on Google (8.8.8.8), Cloudflare (1.1.1.1), and Quad9 (9.9.9.9), as a single record with no duplicates:
_railway-verify.payments.fiveam.music. TXT "railway-verify=575ef24d057337971488b6af07052b80eed7e169b5ae07bfa33f4abdb5431236"
There's no CAA record blocking issuance. The edge currently serves the default *.up.railway.app cert and returns 404 Application not found, so the domain hasn't been bound.
Could you re-trigger verification / cert issuance on your end? I'd prefer not to delete and re-add the domain since that rotates the verify token and CNAME target, forcing the customer to redo their DNS unnecessarily. (you should just add this in app)
Also i think the service thing in this form is broken - it wont let me choose prod. It's habitat-railway /web / prod
Thanks!
Pinned Solution
2 months 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.
5 Replies
2 months ago
This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.
Status changed to Open Railway • 2 months ago
2 months 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 months ago
I'd prefer not to delete and re-add the domain since that rotates the verify token and CNAME target, forcing the customer to redo their DNS unnecessarily. When this is clearly a railway issue. Its been 72 hours since these have been updated.
2 months ago
Well, unfortunately, your only option here is to attempt to remove and re-add the domain.
2 months ago
Thats a terrible customer experience when something is clearly broken on your end, it would take you all 5 min to vibe code a "retry verification" button.
2 months ago
I was wrong, it doesn't regenerate the dns values when removing and re adding so that fixed the issue. That should be documented somewhere.
Status changed to Solved 0x5b62656e5d • 2 months ago