Reserve IP Addresses / Make sure we can keep an IP if we recreate a droplet.
When destroying a droplet there's a 99% chance that you will get your IP back. If someone creates a droplet while destroying/creating a new one and steals your IP, it's a pain, even if the chances are <1%.
This 1% is too much for some. An IP is an important number, your server might not be able to send emails if the last IP's user was sending spam through it.
Software licenses are also tied to IP sometimes.
When I want to rebuild a server (or resize: disk size) I want to make sure that I get my IP back.
Please figure out a way so that we don't lose our IP (100% guaranteed) when we destroy/recreate a droplet.
roger pack commented
I had a related thought--a cheaper cost for a droplet if it has no dedicated IPV4 (just uses a floating) :)
It will great help.
Ben Yanke commented
Please do add. Even at a cost, it's worth it for some people.
AdminRafael Rosa (Admin, DigitalOcean) commented
Perhaps our Floating IPs would solve your problem, they allow you to reserve an IP, assign it to a Droplet and keep it around even if you destroy the Droplet. You can find more info on:
Let us know if this solved your problem.
We would like to have ability to reserver the IPs for our droplets.
Zachary DuBois commented
Still hoping for this, Floating IPs are great but until they replace the actual IPs that get assigned to the VM, this is needed.
take remote database for example. i have to change all the IP's, database user when i spin up the droplet from snapshot. and for a development stage i have to go through this at least for a week. please bring a solution to keep the IP.
Nicolas Grilly commented
Isn't it solved by floating IPs?
Arkar WINN MINN HTWE commented
+3 for this. This is quite critical since we all are working with "Servers" where IPs are fundamentally essential components! They need to be able to be RESERVED!
+3 for this one...
+3 Everytime I destroy my droplet and create a new one right away, I never get the same ip. Even if give it the same namespace. I don't know what I am doing wrong but reserving my ip would bring me peace of mind
David Reagan commented
Also, let us reserve our private ip's. I use iptables to whitelist what private ip addresses are not blocked, so if something happens and I have to rebuild the vm from scratch, I really need to be able to have the same ip addresses. Otherwise I'd have to up date all my other droplets at the same time.
Thomas Meadows commented
i'm sure people would pay a nominal fee to secure a permanent IP address. This is a revenue generator, It should be top priority.
+1 I use remote services that require my droplets IP address is manually whitelisted. I would like to be able to migrate from one droplet (OS) to another without needing to whitelist additional IP's and keep the original droplet online throughout the migration.
Probably should just make a ip market, where you can reserve IP and pay for them event if you don't use it!
Have been waiting for months.
I have 600+ sites I want to migrate to DO. This is the only thing keeping me from doing it. I want to have a load balancer that all my sites point to, but that is very risky since I may not get the same IP if it becomes necessary to re-provision the load balancer.
Leo Winter commented
Ahmed Hassan commented
The best way is able to get IPs and assign them to the droplets we want. If we have an IP and do not use, charge for that so that no one will hold an IP without assigning to a droplet. In this way we can be sure that our IP remains in our account until we release them :)
It would be nice when you destroy and create a droplet to be optional to use the same IP, as sometimes it creates undesirables network problems (please see https://digitalocean.uservoice.com/forums/136585-digitalocean/suggestions/6818942-choose-if-you-want-to-use-the-same-ip-when-destroy )