3 months ago
Hi,
I'm trying to connect a custom domain to my Railway service but the domain remains stuck on "Waiting for DNS update".
Domain:
Railway expected DNS configuration:
CNAME
www → 6ohstsgg.up.railway.app
TXT
_railway-verify.www
railway-verify=e4cca3b4a657e6f4ab09cf64154e...
Verification checks:
nslookup -type=TXT _railway-verify.www.sensi-collaboration.fr
returns the correct railway-verify value.
Public DNS lookup tools also confirm that both the TXT record and the CNAME are visible.
Steps already attempted:
- waited several hours
- removed and re-added the custom domain multiple times in Railway
- verified DNS propagation
The Railway dashboard still shows:
"Waiting for DNS update"
Project:
sensi-collaboration
Service:
web
Could you check if the domain verification cache might be stuck for this project?
Thanks!
11 Replies
Status changed to Awaiting Railway Response Railway • 3 months ago
3 months ago
If you want to use the @ or www domain, you must add both records.
Some DNS providers don't support CNAME flattening (using CNAME records on root domain), so in that case, I'd try migrating to Cloudflare's DNS service and see if that helps.
https://developers.cloudflare.com/dns/zone-setups/full-setup/setup/
3 months ago
Hi,
I updated the DNS configuration as requested.
Current DNS configuration:
CNAME
www → r871ylua.up.railway.app
TXT
_railway-verify.www → railway-verify=e4cca3b4a657e6f4ab09cf64154e...
DNS propagation is confirmed.
nslookup result:
→ 151.101.66.15
Public DNS lookup tools also confirm the correct CNAME resolution.
However the Railway dashboard still shows:
“Waiting for DNS update”.
Could you please check if the domain verification cache might be stuck for this project?
Project: sensi-collaboration
Service: web
Thank you!
3 months ago
Hi,
I’ve now fully updated the DNS records to exactly match what Railway currently requests.
Current Railway requested records:
- CNAME: www → r871ylua.up.railway.app
- TXT: _railway-verify.www → railway-verify=e4cca3b4a657e6f4ab09cf64154e...
Current DNS at IONOS matches exactly:
- CNAME: www → r871ylua.up.railway.app
- TXT: _railway-verify.www → railway-verify=e4cca3b4a657e6f4ab09cf64154e...
Propagation is confirmed externally.
nslookup www.sensi-collaboration.fr returns:
- canonical name: r871ylua.up.railway.app
- address: 151.101.66.15
Public DNS lookup tools also confirm the same CNAME resolution.
However, Railway still shows:
“Waiting for DNS update”
Since the DNS now exactly matches Railway’s requested records and propagation is confirmed, could you please manually check or clear the domain verification cache for this project / service?
Project: sensi-collaboration
Service: web
Domain: www.sensi-collaboration.fr
Thank you.
3 months ago
For further information, currently I have => "railway-verify=e4cca3b4a657e6f4ab09cf64154e..."
PS C:\Users\guibs\Documents\global\public> nslookup www.sensi-collaboration.fr
Server: box
Address: 192.168.1.1
Non-authoritative answer:
Name: r871ylua.up.railway.app
Address: 151.101.66.15
Alias: www.sensi-collaboration.fr
PS C:\Users\guibs\Documents\global\public>Thank you for your help. Guillaume.
3 months ago
Again, as mentioned above, if you wish to use www, you'll also need to add @ records to your DNS provider.
Some DNS providers don't support CNAME flattening (using CNAME records on root domain), so in that case, I'd try migrating to Cloudflare's DNS service and see if that helps.
https://developers.cloudflare.com/dns/zone-setups/full-setup/setup/
3 months ago
@ OP
Add root and www. Cname flatten - try Cloudflare if your host (like godaddy) wont allow cname on the root.
3 months ago
Hi,
Just to clarify: I only intend to use the www subdomain, not the root domain.
Current DNS configuration:
CNAME
www → r871ylua.up.railway.app
TXT
_railway-verify.www → railway-verify=e4cca3b4a657e6f4ab09cf64154e...
DNS propagation is confirmed:
nslookup www.sensi-collaboration.fr
→ 151.101.66.15
External DNS lookup tools confirm the same.
Since the DNS configuration matches exactly what Railway expects, could a staff member please check if the domain verification for this project might be stuck?
Project: sensi-collaboration
Service: web
Domain: www.sensi-collaboration.fr
Thank you.
3 months ago
LOL, yes bro, but domain.com must resolve to somewhere first, then domain.com can tell the world to 307 to www.domain.com
Try make domain.com online with A-record first.
https://www.whatsmydns.net/#A/sensi-collaboration.fr
Attachments
3 months ago
Hi there, all is fine for now, thank you for your help ! 🙂
Guillaume.
Status changed to Solved jr • 2 months ago
