Custom domain www.goby2.com stuck on "Waiting for DNS update" for 2+ days despite fully verified DNS
gobyllc2026
HOBBYOP

a day ago

Custom domain: www.goby2.com

Project: production

Service: goby-backend

Issue:

The custom domain has been stuck on "Waiting for DNS update" for over 2 days.

DNS records configured in GoDaddy (registrar):

  • CNAME: www → cxsweqz3.up.railway.app
  • TXT: _railway → railway-verify=98733b464cc6432da028953b07954e9ec1571449bd9d950fc4d7bb01f4f3e2be

Verification done:

  • Confirmed both records are byte-for-byte identical to what Railway's dashboard shows
  • Confirmed via whatsmydns.net that both records are fully propagated globally (100% green across all regions/resolvers)
  • No conflicting old CNAME/A records for "www" in GoDaddy
  • Restarted deployment - no change
  • Values in Railway dashboard match GoDaddy exactly

I have not deleted/re-added the domain yet in case this triggers a Let's Encrypt rate limit issue, since I understand there's a 5 certificates/week limit per hostname.

Could you please check on your end if:

  1. There's a stale validation state for this domain
  2. We've hit any certificate issuance rate limits
  3. There's a way to manually re-trigger verification without deleting the domain

Thank you!

$10 Bounty

1 Replies

Railway
BOT

a day ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway 1 day ago


Your TXT record needs to be on _railway-verify.www, not _railway.


Welcome!

Sign in to your Railway account to join the conversation.

Loading...