14 days ago
Subject: Custom domain TXT verification stuck for 1+ hour despite correct DNS
Hi, I'm trying to connect a custom domain and the TXT verification record has been stuck in "pending" for over an hour, even though the DNS is confirmed correct.
Domain: www.culturecapitalllc.com
Project: culturecapitalllc
Status:
CNAME (www → hkkwhwe9.up.railway.app) — verified ✅
TXT (_railway-verify.www) — still pending ⚠️ (1+ hour)
I've verified the DNS is correct by querying the authoritative nameserver directly (bypassing all caching):
Query: TXT _railway-verify.www.culturecapitalllc.com @ns.gabia.co.kr
Result: railway-verify=1a22f37e051752da60f0d0ff96172d3f55e7c6abdc89d3eecfdc484e5e12bac4
This exactly matches the value Railway requested. I've also confirmed:
No duplicate/conflicting TXT records at that hostname
No DNSSEC configured on the domain
Railway status page shows all systems fully operational
Could someone please manually check what's blocking verification, or trigger a re-check? Happy to provide any additional info needed.
Thanks!
Attachments
1 Replies
Status changed to Awaiting Railway Response Railway • 14 days ago
14 days ago
I’m able to access your site just fine. It sometimes may take up to a few hours to validate the domain.
14 days ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 14 days ago