Custom domain stuck on "Waiting for DNS update" — TXT verification not being detected
gurmysirha
FREEOP

a month ago

Hi team,

My custom domain has been stuck for several days despite DNS being correctly configured and globally propagated.

Service: bhabhi-io-production.up.railway.app

Custom domain: www.bhabhi.io

Railway's required CNAME target: mnpo4w5x.up.railway.app

Status in dashboard:

CNAME www → green checkmark ✓ (verified)

TXT _railway-verify → warning ⚠️ (NOT verified, but the record exists and is correct)

DNS config in Cloudflare (set to DNS only / unproxied):

CNAME www → mnpo4w5x.up.railway.app

TXT _railway-verify → railway-verify=280907a8f4cbecf461901990c29f72a9ae8801534ea7e6f9709b51261426adbe

Verified globally from multiple resolvers:

$ dig @1.1.1.1 www.bhabhi.io CNAME +short

mnpo4w5x.up.railway.app.

$ dig @8.8.8.8 _railway-verify.bhabhi.io TXT +short

"railway-verify=280907a8f4cbecf461901990c29f72a9ae8801534ea7e6f9709b51261426adbe"

The TXT value matches exactly what the dashboard shows. Records have been in place for 72+ hours.

Already tried:

Toggled Cloudflare proxy off (grey cloud / DNS only)

Edited and re-saved both records

Waited multiple days for propagation

Verified from Cloudflare's own authoritative nameserver (faye.ns.cloudflare.com)

Note: I cannot delete and re-add the domain because I've hit the custom domain limit on my plan.

Could someone please clear the verification cache or investigate why the TXT check keeps failing?

Thanks!

Solved$10 Bounty

2 Replies

a month ago

_railway-verify.www.bhabhi.io not _railway-verify.bhabhi.io


gurmysirha
FREEOP

a month ago

Ah brilliant! That worked 🙂

Thank you


Status changed to Solved brody about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...