Skip to content
Subject: Custom domain stuck on “Waiting for DNS update” despite correct DNS records
mithilajewellery-byte
OP

a month ago

Hello Railway Support,

My custom domain mithilajewellery.com has been stuck on “Waiting for DNS update” for over an hour.

Service: virtuous-courage

Environment: production

Domain: mithilajewellery.com

Target: pz4bsc4g.up.railway.app

Railway domain ID: 924d64a7-f780-4224-bb41-0f9104ada416

I have verified the DNS configuration:

The apex CNAME points to pz4bsc4g.up.railway.app.

The _railway-verify TXT record matches the verification token shown by Railway.

Both records resolve publicly through Google DNS.

The TXT record also resolves directly from Cloudflare's authoritative nameserver, dahlia.ns.cloudflare.com.

The apex CNAME is currently set to DNS only in Cloudflare.

The Railway CLI reports Sync status: ACTIVE, but Verified: no and Certificate status: CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP.

Could you please check the domain verification status on your side and re-trigger ownership verification and certificate issuance if necessary? I would prefer not to delete and recreate the domain because the DNS records are already configured correctly.

Thank you.

Solved

1 Reply

Railway
BOT

a month ago

The TXT record at _railway-verify is publishing a truncated token: it currently ends at ...d896, so it doesn't match and ownership verification can't pass.

Update that TXT record in Cloudflare so its value is exactly railway-verify=a5767036d9258a498685ebf5b9d8963fff03b91ae89cc85de483680efd90a0fe, with no characters missing. Verification and certificate issuance resume on their own once the corrected value propagates, so there's no need to delete or recreate the domain.


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


Railway
BOT

a month 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 • about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...