Skip to content
Custom domain stuck "Waiting for DNS update" for 4+ hours
lemilion321-cell
OP

5 days ago

My custom domain www.lepost.my.id has been stuck on "Waiting for DNS update" for 4+ hours on Trial plan.

Both DNS records are correctly configured and fully propagated globally (verified via dnschecker.org):

  • CNAME www → szbir4sk.up.railway.app ✅
    • TXT _railway.www → railway-verify=6aabe8e2bde24beb1697866466c7193701775ccf381f84dd68bfe560d5382eca ✅

Please help verify/provision the domain manually.

Awaiting User Response

1 Reply

Railway
BOT

5 days ago

Your CNAME record is correct and propagated, but the TXT verification record is on the wrong host: it was added as _railway.www, and it needs to be at _railway-verify.www. Create a TXT record with host _railway-verify.www and value railway-verify=6aabe8e2bde24beb1697866466c7193701775ccf381f84dd68bfe560d5382eca (you can remove the _railway.www one). Once it propagates, verification and certificate issuance continue on their own.


Status changed to Awaiting User Response Railway • 5 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...