21 days ago
TXT verification is failing consistently while CNAME verification succeeds for www.guidelab.app. DNS is correct, globally propagated, and verified from independent sources (Google's public resolver 8.8.8.8 and Cloudflare authoritative NS). Issue reproduced identically across two separate domain-add attempts with different tokens and TXT locations, suggesting a Railway-side TXT validator issue.
Details:
Domain: www.guidelab.app
DNS Provider: Cloudflare
TTL: 300 seconds (both records)
Project: attractive-strength
Service: @guidemaker/marketing
Environment: production
Verified DNS Records (both attempts):
TXT at _railway-verify.www: railway-verify=2f1b428fe8f244f87836fcd6ad30f894ae0b8acb8abad607e5719672d0eb99dd
CNAME at www: of6jzv4l.up.railway.app
Validation (matches from both 8.8.8.8 and kai.ns.cloudflare.com):
First attempt: TXT at www → CNAME verified, TXT failed
Second attempt: TXT at _railway-verify.www (fresh domain-add) → CNAME verified, TXT failed again
Both attempts identical CNAME-pass/TXT-fail split despite different tokens and locations
Suspected cause: Bug or state issue in Railway's TXT verification backend for this account/domain.
4 Replies
21 days ago
Your TXT record at _railway-verify.www.guidelab.app is correctly set and matches the expected token. The issue is with the CNAME: our system sees www.guidelab.app pointing to guidelab.app (your apex) rather than directly to of6jzv4l.up.railway.app. This likely means the www CNAME in Cloudflare targets the apex, which then resolves onward to Railway, but we need the www record to point directly to of6jzv4l.up.railway.app. Please update that in Cloudflare and ensure proxy is disabled (grey cloud / DNS-only) for the www record, then reply here once it is updated so we can verify the change.
Status changed to Awaiting User Response Railway • 21 days ago
21 days ago
That doesn't match what I'm seeing right now. Just re-verified (timestamp: Jul 31, 2026 1:11 PM) via both a public resolver and my DNS provider's own authoritative nameserver directly:
dig www.guidelab.app CNAME @8.8.8.8 +short
of6jzv4l.up.railway.app.
dig www.guidelab.app CNAME @kai.ns.cloudflare.com +short
of6jzv4l.up.railway.app.
www.guidelab.app resolves directly to of6jzv4l.up.railway.app — there's no apex hop involved. This is a fresh lookup, not cached. What you described (www pointing to the apex) matches the domain's original configuration before I moved DNS to Cloudflare and fixed the CNAME — is it possible your system is checking against stale/cached DNS data from before that change? Can you force a fresh re-check?
Status changed to Awaiting Railway Response Railway • 21 days ago
21 days ago
Hey, I just took a look, and everything does seem fine now.
Sometimes our TLS issuance can take awhile due to the nature of DNS propagation. When I query your domain I see the correct records now and it looks like your site has a valid certificate as well now too. Anything else we can help with?
Status changed to Awaiting User Response Railway • 21 days ago
21 days ago
yes, everything looks good now. Thank you!
Status changed to Awaiting Railway Response Railway • 21 days ago
Status changed to Solved nicthib • 21 days ago