a month ago
Affected projects:
- courageous-mindfulness → business.orionsystem.app
- sublime-delight → resto.orionsystem.app
- affectionate-kidness → suite.orionsystem.app
- robust-amazement → market.orionsystem.app
What happened:
- All domains were working correctly before.
- Railway changed the internal CNAME values (e.g. from orion-demo-production.up.railway.app to vmwphthd.up.railway.app).
- I updated all DNS records in Cloudflare with the new CNAME and TXT values provided by Railway.
- Despite the DNS records being correctly configured in Cloudflare, Railway still shows a warning on all domains and they are not resolving.
I have tried:
- Updating CNAME and TXT records in Cloudflare with the exact values Railway provided
- Switching between Proxied and DNS Only in Cloudflare
- Deleting and re-adding the domains in Railway
- Manual redeployments
The frontend loads via the Railway internal URL (*.up.railway.app) but not through the custom domains.
Could you please help me resolve this? These are production domains for a live SaaS application with active customers.
Pinned Solution
a month ago
Upon doing a dig NS orionsystem.app @1.1.1.1 I get a failed-whois-verification.namecheap.com., so I think you have some pending verification on namecheap.
6 Replies
a month ago
This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.
Status changed to Open Railway • about 1 month ago
a month ago
Hey, I just did a nslookup on all of the domains you mentioned and I don't see any CNAME and or TXT records, only an A record and NS records, both pointing to Namecheap and that's likely the main issue, the NS records still point to namecheap, not Cloudflare.
You should either move your DNS to Cloudflare or stay on Namecheap.
medim
Hey, I just did a nslookup on all of the domains you mentioned and I don't see any CNAME and or TXT records, only an A record and NS records, both pointing to Namecheap and that's likely the main issue, the NS records still point to namecheap, not Cloudflare. You should either move your DNS to Cloudflare or stay on Namecheap.
a month ago
Thank you! After running nslookup myself, I can confirm the DNS is still resolving through Namecheap instead of Cloudflare, even though the nameservers in Namecheap are set to Cloudflare (alla.ns.cloudflare.com and leonidas.ns.cloudflare.com) and Cloudflare shows the domain as Active. It seems the nameserver propagation is still incomplete. Is there anything I can do to speed this up, or should I just wait for full propagation? Thank you
santinoantonini-create
Thank you! After running nslookup myself, I can confirm the DNS is still resolving through Namecheap instead of Cloudflare, even though the nameservers in Namecheap are set to Cloudflare (alla.ns.cloudflare.com and leonidas.ns.cloudflare.com) and Cloudflare shows the domain as Active. It seems the nameserver propagation is still incomplete. Is there anything I can do to speed this up, or should I just wait for full propagation? Thank you
a month ago
Upon doing a dig NS orionsystem.app @1.1.1.1 I get a failed-whois-verification.namecheap.com., so I think you have some pending verification on namecheap.
a month ago
Issue resolved! The domain was suspended due to a pending WHOIS verification required by ICANN. I contacted Namecheap support and they resent the verification email, which I completed successfully. The domain should be fully propagated within 24-48 hours. Thank you for your help in diagnosing the issue!
a month ago
I can see that all your domains are now working as expected! Marking this as solved.
Status changed to Solved medim • 29 days ago