a month ago
Dashboard shows "Waiting for DNS update" for my domain, but both required DNS records are correctly published and verified via dig against the domain's authoritative nameservers (Combell):
CNAME sandbox → zd7n63bl.up.railway.app ✓
TXT _railway-verify.sandbox → railway-verify=39f1491e910ab950ecb1724ab8078ec8c444ee2d15ca481939e1fac7efa20614 ✓ (resolving correctly on all 3 Combell nameservers)
It's been over an hour since the TXT became resolvable and the dashboard still shows the warning — no dedicated Let's Encrypt certificate has been issued (connection still serves the fallback *.up.railway.app wildcard cert). I also tried a manual port-toggle re-save on the domain to trigger re-verification, with no effect.
Can you manually trigger DNS re-verification / cert issuance for a domain?
Pinned Solution
a month ago
What domain are you trying to use?
Also, 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.
1 Replies
a month ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 1 month ago
a month ago
What domain are you trying to use?
Also, 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.
Status changed to Solved 0x5b62656e5d • 7 days ago