4 hours ago
Hello,
I'm experiencing an issue with my custom domain on Railway.
Domain:
The domain has already been added to my Railway service and the service has been redeployed.
Current status:
The custom domain remains stuck on:
"Waiting for DNS update"
The TLS certificate is never issued.
Here is everything that has already been verified:
• The application deploys successfully.
• The Railway deployment is healthy.
• The application is fully accessible at:
https://lnxbeats-site-production.up.railway.app
DNS configuration (OVH):
CNAME
→ x7f4gmvy.up.railway.app
TXT
_railway-verify.www.lnxbeats.fr
→ TXT verification record configured exactly as provided by Railway.
The DNS has fully propagated.
Verification performed with Cloudflare DNS (1.1.1.1):
dig @1.1.1.1 www.lnxbeats.fr CNAME
returns:
www.lnxbeats.fr. CNAME x7f4gmvy.up.railway.app.
Verification of the TXT record:
dig @1.1.1.1 TXT _railway-verify.www.lnxbeats.fr
returns exactly ONE TXT record.
There are no duplicate TXT records.
Additional information:
- CNAME is correctly resolved worldwide.
- TXT verification record is correctly resolved worldwide.
- The service is healthy.
- The application is online.
- The custom domain has already been attached to the service.
- The service has already been redeployed after attaching the domain.
Despite all of this, Railway still displays:
Waiting for DNS update
and no TLS certificate is issued.
Could someone please check the internal domain verification logs and manually revalidate the domain if necessary?
It looks like Railway is not completing the TXT verification even though the DNS records are publicly available and correctly configured.
Thank you very much for your help.
3 Replies
Status changed to Awaiting Railway Response Railway • about 4 hours ago
4 hours ago
I don't see a TXT record for your domain on my DNS lookups either. If you're sure it's configured properly then it's worth waiting more, the DNS might still be propagating
4 hours ago
Thank you for checking.
The TXT record is currently visible from Cloudflare's public DNS resolver (1.1.1.1).
I ran:
dig TXT _railway-verify.www.lnxbeats.fr @1.1.1.1
and it returns exactly one TXT record with the Railway verification value.
So it looks like the record may not yet have propagated to every resolver.
I won't change the DNS configuration and will wait for propagation to complete.
For reference, my DNS provider is OVHcloud, not Cloudflare. I only used Cloudflare's 1.1.1.1 resolver to verify public DNS propagation.
I'll check Railway again later.
Thank you for your help.
Status changed to Awaiting Railway Response Railway • about 4 hours ago