15 days ago
I’m trying to verify the subdomain pay.nasco-inc.com, and the CNAME record is working correctly, but the TXT verification is failing even though it is properly configured and publicly resolving. The CNAME pay → mmcj4rif.up.railway.app resolves as expected. The TXT record _railway-verify.pay → railway-verify=abc...db is also correctly set and accessible. I confirmed this using dig, including a full trace, and it returns the exact expected value directly from the authoritative nameserver (ns1.netfirms.com), which confirms the record exists, matches exactly, and is fully propagated.
- CNAME resolves correctly for pay.nasco-inc.com
- TXT record is set exactly as provided by Railway
- dig +trace TXT _railway-verify.pay.nasco-inc.com returns the correct value from authoritative DNS
- Record is publicly accessible and not a propagation issue
Can you confirm what hostname your verification system is querying, re-run or reset the verification on your end, and check for any caching or mismatch in your DNS resolution layer?
Pinned Solution
15 days ago
I’m able to access pay.nasco-inc.com perfectly fine on my browser. You could try removing the domain from Railway, and add it back after about 10-15 mins, but I’m guessing your dashboard may or may not be displaying stale icons.
2 Replies
15 days ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open Railway • 15 days ago
15 days ago
I’m able to access pay.nasco-inc.com perfectly fine on my browser. You could try removing the domain from Railway, and add it back after about 10-15 mins, but I’m guessing your dashboard may or may not be displaying stale icons.
15 days ago
lol ofc this happens the moment I create a ticket. Well thanks for help regardlessly
Status changed to Solved mykal • 15 days ago