Preserving IP address when cloning server - making scaling down hassle-free
Scaling up is easy.
Scaling down (with Vultr, DigitalOcean or Linode) requires to clone a server.
When cloning, server gets new IP address - this causes a lot of hassle with application integration or DNS configuration.
SUGGESTION:
It would be great to make scaling down hassle-free, so that after cloning server could have the same IP as previous server.
Adam
shared this idea
-
Christopher Burns commented
This is a huge one for me -- but not just because of downgrading.
I have over 120 websites running on Debian 11, which loses support on August 31, 2026. On Cloudways, we update the OS by cloning the server.
If I have to clone the server and then work with clients to update their DNS records -- it'll be months of work and back and forth communication.
I would happily pay for a reserved IP address on each server so that the cloned server automatically receives the same reserved IP address.
-
Ryan Lovett
commented
This is a limitation of the server provider, well at least Digital Ocean that I know of. You can't scale down on Digital Ocean without having to spin up a new droplet (which results in a new IP) so I can see Cloudway's limited ability to address this, but you're right that it would be nice to not have to update records for all domains.