Custom domain stuck on "Waiting for DNS update" for 24+ hrs — same issue as solved thread 942cae36
nikhilwagh1018
HOBBYOP

10 days ago

Custom domain cycleaudit.parisar.org on my Parisar service has been stuck on "Waiting for DNS update" (specifically the TXT record) for over 24 hours.

DNS is confirmed correct via multiple resolvers:

  • nslookup -type=CNAME cycleaudit.parisar.org 8.8.8.8 → resolves correctly to 4idz5o0w.up.railway.app
  • nslookup -type=TXT _railway-verify.cycleaudit.parisar.org 8.8.8.8 → returns exactly one matching value: railway-verify=4423e77e47cc40538993151bd9abec7e9186f57e03f9e6d603d00f02a202a697
  • Also confirmed via dnschecker.org across multiple global locations

No duplicate records exist. This looks like the same issue reported and resolved here: station.railway.com/questions/custom-domain-stuck-on-waiting-for-dns-942cae36 — chandrika (Railway staff) confirmed that case as "the verification workflow stalled before it could pick up the records" and fixed it via a manual certificate re-issuance.

Could someone do the same for my domain?

Project: aware-tranquility

Service: Parisar

Domain: cycleaudit.parisar.org

Solved

0 Replies

Status changed to Awaiting Railway Response Railway 10 days ago


Status changed to Solved nikhilwagh1018 10 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...