I should be able to create new droplets and assign the IP of an old droplet to a new one.
In last couple of months I needed to create 3 new server + I have 2 couple of years old server and all 5 IP addresses that I got are blocked in many places due to which email from those IP are not getting sent. People are just misusing an IP, once they get blocked, so they just recreate a droplet and get new IP to play with.
And today I ran into a problem with one of my old server and had to destroy that server and need to do a fresh install. I wanted to keep my old IP as I have been using that IP from few years now. But I couldn't find any option to get that IP back, now I have to reassign new IP in many domains and places.
Sorry, but I don't agree tottally with you.
There are situations where you really need to keep the same ip address, imagine having a dns server and need to scale this out, it's takes time to change ip address with registers (verisign, godaddy, etc)
also andre, when you do a dns change at go daddy. When it changes where its pointed, you wont see a downtime as long as both servers are up with the content on it. When i do DNS changes from godaddy it usually swaps within 15-30 minutes. And I never even notice unless I have a file on the new FTP that isnt on the old one. Because it doesnt actually take the original A record down when applying the new one. It just swaps from one to the other.
I suppose I have no choice but to do that. I'm just saying it was easier on aws ;)
Interesting case, technically speaking you can create everything you want on the new server. Then take a snapshot of it.
Destroy both servers and create the new server from the snapshot and it will give you back your used IPs, I would test this outside of your production server first of course.
Or, what you could do is setup nginx as a proxy as you mentioned and it can query either the new or old IP.
Also depends on how often you do this.
If it happens rarely I would say just setup the new server, point DNS to the new machine, and deploy a simple nginx config on the old server to act as a pass through proxy to the new IP.
When traffic dies down on the old IP just destroy the server.
I understand. Here's some context on what I'm trying to achieve - maybe you can make a suggestion.
I have a domain on godaddy that points to an IP of a droplet. I need to make significant changes on my droplet that require downtime. What I would do is create another droplet, make the changes I need on the new one and then just switch IPs of the 2 machines.
I cannot tell godaddy to point the domain to a different IP, because that DNS change take a lot of time to propagate.
There probably are other solutions (like using a load-balancer in front of server machines), but we don't need such a complex system at the moment.
The point of my suggestion was to give users more flexibility in managing their machines.
Don't be so attached to the IP.
If its meant to be it will cycle back to you, if not it never loved you in the first place.
But honestly, the answer is that we just designed it a different way with a best case effort to return an IP you used prior.
Perhaps I didn't express myself right - what I wanted to say is to give the user the ability to manage IP addresses as he pleases, like on aws.
The backend automatically attempts to return a previously used IP to you, if it doesnt get reassigned it's because it has already been cycled through.
You won't be notified about changes to this idea.