Stuck custom domain verification
joshstroma-byte
FREEOP

a month ago

HI Team πŸ™‚

My domain has been on "Waiting for DNS update" for 24+ hours, despite multiple re-deploys and confirmation DNS is correct and verified β€” I believe the TXT verification is stuck on your side.

CNAME api β†’ 94n6nerp.up.railway.app β€” shows green in the Configure DNS Records dialog.

TXT _railway-verify.api β€” value begins railway-verify=76f832b2... (full value visible via dig, or I can share it in a private/support thread). It shows a warning triangle in the dialog, but the record is live and globally resolvable: dig _railway-verify.api.danahouse.co.uk TXT +short returns it, and it's a character-for-character match to what your Configure DNS Records dialog is asking for.

curl -v https://api.danahouse.co.uk shows Railway serving the default *.up.railway.app wildcard cert β€” no certificate was issued for the custom domain, because verification never completed.

Already tried: a fresh deploy (didn't unstick it). There's no recheck button on the domain row.

Is it possible for you to manually re-trigger / reset verification for this domain. I'd prefer not to delete and re-add it β€” I'm at my plan's custom-domain limit and don't want to risk losing the slot. Can you please re-verify without deletion, or confirm a safe path?

The front-line Agent assistant confirmed the DNS is correct but said it has no tool to re-trigger backend verification and directed me here.

3 Replies

It may take up to a few hours (sometimes maybe even a day) for Railway to validate the DNS and issue a certificate. If a cert isn't issued by then, try removing the domain from Railway and add it back after ~10-15 mins. Update DNS records as necessary.


joshstroma-byte
FREEOP

20 days ago

Following up. 6 days on, still "Waiting for DNS update" and the custom domain still serves 503 / the default wildcard cert. DNS is confirmed correct and globally resolvable (CNAME api β†’ 94n6nerp.up.railway.app green in the dialog; TXT _railway-verify.api matches character-for-character). The only reply so far was from a community member. Can a staff member please manually re-trigger backend verification for this domain, or confirm that remove + re-add is the only path? Verification appears stuck server-side. Linked resource: 9d814a26 / 27d36773 / b7cea93d


Have you tried removing the domain and adding it back after ~10-15 mins?


Welcome!

Sign in to your Railway account to join the conversation.

Loading...