a year ago
When migrating to another Railway account, it is ideal to set up the infrastructure then update the DNS records when ready to ensure a smooth transition from the old service to the new one.
At present, even after the old service is decommissioned, the Custom Domain remains unavailable so long as the old CNAME record is in place. We need to clear out the CNAME record before configuring the new service. This necessitates a significant period of downtime. This also seems unnecessary as the CNAME is unique each time.
It would still be worth showing a warning, e.g.
"This custom domain is already in use by another service on Railway. It will not resolve to this service until you update your DNS records"
"This custom domain is pointing to Railway but is not correct. Please update your DNS records"
2 Replies
a year ago
May I ask why you didn't simply transfer the entire project to the other account? that way you wouldn't need to do anything manually, or even have to redeploy for that matter.
a year ago
The account is managed by a third party and we do not have access to the project.
What we're asking for here would be analogous to configuring a reverse proxy.
