8 days ago
Hi Railway support team,
I've been trying to verify my custom domain www.urbanaura.com.ar for several days now and the TXT verification record remains stuck as pending on Railway's side, even though the DNS records are correctly published.
Current status:
CNAME www → z4334f29.up.railway.app ✅ verified by Railway
TXT _railway-verify.www.urbanaura.com.ar → railway-verify=fabfa72cb31ee36bcf3d3104bc0b6e92fb7cbf90cb21e246e61176887e502e02 ⚠️ still showing as pending
What I've confirmed:
Both Google DNS (8.8.8.8) and Cloudflare DNS (1.1.1.1) resolve the TXT record correctly
There are no duplicate records
The domain is hosted at Donweb (Argentina), and the record name is published as _railway-verify.www.urbanaura.com.ar (the registrar appends the full domain automatically, which is standard behavior)
I've reduced the TTL from 14400 to 900 seconds to help with cache expiration
Railway's verifier does not seem to be picking up the TXT record despite it being publicly resolvable. Could you please check if there's a cache issue on your end or force a re-verification of the domain?
Project: lavish-vitality
Service: urban-aura
Domain: www.urbanaura.com.ar
Thank you!
Pinned Solution
8 days ago
It may take up to a few hours (maybe even a day) for Railway to validate the DNS and issue certificates. If one isn't issued by then, try removing the domain from Railway and add it back after ~10-15 mins. Update DNS records as necessary.
1 Replies
8 days ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 8 days ago
8 days ago
It may take up to a few hours (maybe even a day) for Railway to validate the DNS and issue certificates. If one isn't issued by then, try removing the domain from Railway and add it back after ~10-15 mins. Update DNS records as necessary.
Status changed to Solved 0x5b62656e5d • 8 days ago