14 days ago
Custom domain www.isditaly.it on service "isd-italy-website" (project "website ISD") is stuck on "Waiting for DNS update".
- CNAME www → db7mtzx3.up.railway.app is shown as verified in the DNS records panel.
- TXT _railway-verify.www.isditaly.it = railway-verify=de6a60a385255cebf8d95a5ffee083e17bac3d8c82286c62be37e9ad7be525d3 has been published for several hours (DNS only, Cloudflare zone) and resolves correctly on the authoritative nameservers (kirk/connie.ns.cloudflare.com) and on public resolvers (8.8.8.8, 1.1.1.1), but Railway still shows it as pending.
- No CAA records on the zone.
- Target port 8080 has been set on the custom domain, and the service has been redeployed (region moved to EU West); status unchanged.
- The domain was originally added to Railway several days before the DNS records were created, so verification polling may have stopped.
Result: no certificate is issued, browsers get NET::ERR_CERT_COMMON_NAME_INVALID.
Could you re-trigger the verification? Please advise without requiring domain deletion, as DNS changes go through a third-party team. Same issue as "Custom domain stuck on 'Waiting for DNS update' with valid CNAME and TXT" (solved by a certificate re-issuance on Railway's side).
Attachments
1 Replies
Status changed to Awaiting Railway Response Railway • 14 days ago
14 days ago
The certificate for your custom domain is now valid and the domain is verified and serving traffic correctly (we confirmed a 200 response with a valid Let's Encrypt certificate through our edge). The "Waiting for DNS update" label in the dashboard is a stale display state that should refresh shortly.
If your browser still shows NET::ERR_CERT_COMMON_NAME_INVALID, clear the TLS state cache or try an incognito/private window - browsers cache certificate errors aggressively.
Status changed to Awaiting User Response Railway • 14 days ago
Status changed to Solved brody • 14 days ago