Skip to content
Four custom domains stuck on "Waiting for DNS update" for 24h; API reports propagated
richearl81
OP

a month ago

Hi, four of our custom domains seem to be stuck.

Service: the api service in our production environment.

Custom domains:

go.believeloans.com CNAME -> 0u4sebvp.up.railway.app

go.simplymoney.com CNAME -> o77n5nbi.up.railway.app

go.believeprotect.co.uk CNAME -> 98llayyz.up.railway.app

t.believeprotect.co.uk CNAME -> yq49bi1f.up.railway.app

For every name the CNAME and the _railway-verify TXT are in place with the exact values from the dashboard, confirmed from the authoritative nameservers and public resolvers, with no CAA records and no Cloudflare proxy. The customDomain API reports the CNAME as propagated and the status as checking before issuance, but the dashboard has shown "Waiting for DNS update" for over 24 hours and no certificate has been issued (the names serve the *.up.railway.app certificate). Three other domains on the same service issued normally this week.

Please re-trigger verification and certificate issuance for the four names.

Solved

1 Reply

Status changed to Awaiting Railway Response Railway • about 1 month ago


a month ago

We checked all four domains. For each one, the CNAME and the verification TXT record match the expected values exactly, but ownership verification never re-ran after the records went live. That left them stuck at "Waiting for DNS update".

We've started verification and certificate issuance again for all four. It can take a few minutes to finish, and nothing needs to change on your DNS.


Status changed to Awaiting User Response brody • about 1 month ago


Railway
BOT

24 days ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway • 24 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...