We have the ability to assign floating IP's to a droplet. When we destroy the droplet the IP should not be immediately be released back into the available queue. It should remain attached to your account and orphaned (yes, we get charged which is okay.) Since we retain the floating IP we can spin up a droplet and then assign it to that floating IP.

Real Life Scenario: Droplet is accidentally deleted along with the backups. We spin up a new droplet and restore from a snapshot or off-site backup and we're good to go. However, we need to update DNS to point to the new IP and we have to wait for that to propagate. That's too long to wait.

It would be great.

We're still waiting... :(

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.

Please do add. Even at a cost, it's worth it for some people.

Hello,

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:

https://www.digitalocean.com/community/tutorials/how-to-use-floating-ips-on-digitalocean

Let us know if this solved your problem.

Best regards
Rafael

We would like to have ability to reserver the IPs for our droplets.

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.

Isn't it solved by floating IPs?

+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!

PLEASE!

+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

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.

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.

Absolutely necessary!

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 )

In desperate need of an update for this one. Thanks.

any update or ETA ?

Would it be possible to get an update/ETA on this?
We got stung by this very issue tonight while resizing a droplet to the next size up, due to having to perform the droplet resize work-around; once back after a ~47minute snapshot (~53minutes for one previous a few days prior) and a 25minute create, amounting to well over an hour downtime for a production site just for a change in server capacity which is supposed to take...far less time according to the fast resize option... Ok, so fair enough, we have a 60GB disk at ~50% capacity, so that's gotta take some time, just no way around that, Ok, I can deal with that, that's just the way things are...but then we get back up and we've lost our IP and are facing more downtime still while DNS propagates... ok stuff happens, you guys are still ramping up features working out kinks and putting together the best service you can for your customers based on the needs they have, and putting together an otherwise really fine service too I must say, we're otherwise really happy with everything you guys are doing and understand there are hiccups along the way, but we're now on the edge of having to move elsewhere for business risk reasons due to this occurring as we have investors to answer to - I understand things sometimes don't work perfectly, but please allow us a safety net for when they don't, the occurrence of an "unfortunate series of events" so to speak of a few things not-going-quite-right can really ruin someone's day. Please help us stay with you guys, we love what you're building, but no doubt you understand what the "beancounters" can be like.
Cheers,
-Matt.

+1 on this. Especially since at the moment the only way to add disk space to your server is to (re)create. Not having this feature is actually stopping us from upgrading servers with DO (and therefore spending more money with them).

Is there any news on this? Given the current DNS propagation issues this would be an extemely useful addition to the service.

At least if you keep that ip reserved until we launch a new droplet, don't need to last forever but as Dries says, have a peace in mind that we will get that particular IP again

Have notice that when I launch a new droplet I get my ip back and that is awesome... but what if I don't? :'c

Thanks for the efforts!

Thank you! This worried me when I made a new droplet. Some things like TeamSpeak NPL licences are locked to IP and it can take a very long time to get in contact to swap licenses around.

What you could do is provide a mandatory choice at deletion time where we select if we wish to keep the IP of the droplet and inform us it will be reserved for X days. Then when we create a new droplet, if there are unused reserved IP's on our account we can choose which IP to assign to the new droplet during the creation or a second step after it.

This is great news!!! Kindly ensure to include the Private Network IP along with the more visible Public IP in this reserved IP provisioning. Thank you very much for your efforts.

هات ماعندك

it is very important. +3 votes.

Yes, especially for IP-tied licenses (e.g. DirectAdmin panel software).

IMO This should not be implemented by default. I think DO should offer this as a separate service, allow purchasing IPs (Maybe $1/mo each) that you can apply to droplets if you want.

Generally I do not want to get the same IP again, as reconnecting to SSH flags the server because the fingerprint no longer matches since last connecting to it. I have to go into my known_hosts file and delete it to be able to connect to it again.

Regarding my last comment, you can have the TTL usually set at 86400 (one day), but drop to 60 seconds in anticipation of a potential IP-change - then a day later do the re-creation, update the IP, then set the TTL back to 86400.

Have a "mission critical" droplet that runs a DNS server :D PowerDNS+PowerAdmin is a nice combination.

You can then set the TTL of your other droplets' A-records to 60 seconds, ensuring that an IP change only causes a minute of outage at the most (on top of the outage caused by destroying/recreating the droplet).

Obviously, the "mission critical" $5/month droplet should never need to be re-created as it only runs simple stuff (mine runs DNS server + email receiver + automated git backups of config from other servers)

This is important, can we have some feedback on it?

I voted on this one and the move VM to VM, even though the rebuild option exists now. Rebuild doesn't work if you want to keep a machine running while you set up a new version of it. Just signed up, started a server, then stopped it. Without this feature, there is no true "scaling" since I can't move my public IP around. Sorry DO, without this I can't use you.

+3 this is absolutely necessary.

As Wayne Hartman has mentioned. So this

+3 if you can add routes to use custom IP blocks. RIPE has already been mentioned. But I personally have a block reserved with ARIN. Please DO, make this happen!

https://www.arin.net/fees/fee_schedule.html

We need this.

I'll go a bit further with this... It would be nice to be able to use our own IPs as well (registered with RIPE)

Agree, I will pay money for reserve ip.

I also just can agree. We are very satisfied with the whole service so we are planning to expand our plan and droplet size. But we already registered some licenses which are tied up with the IP. (Our Teamspeak License as example).

It really would be very unfortunate if problems occur there.

I don't know if keep the same after destroy ( you destroy for something xd )

I will be glad to pay more for reserve ip like in an external module, like DNS module, the capability to reserve an IP would be nice

at least reserve an already in use ip from our drops

I was really disappointed to hear that if I wanted to enable automated backups I would have to take a snapshot, then destroy the droplet and created a new one using the snapshot.

This wouldn't be that big of a deal if I was guaranteed to keep the same IP, but that is not the case.

We currently have over 25 droplets and are starting to work with the API so we can destroy and create automatically and making sure the keep the same IP is critical. When will we get 100% the guarantee?

Agreed, this is an important feature especially in a potential business environment where downtime is money +1

for those who need quick fix - use CloudFlare DNS and API, you can manage and correctly set A records in seconds (and it works in seconds)

This is something that needs to be implemented +1

It's very important thing +1

Nice one, and @Morthawt's idea on implementing a solution sounds great

+1;It is not a game - if resizing production due to lack of disk space only -it is 100% SHOULD GIVE SAME IP. Cannot risk with 3 days when DNS updates if IP is not reserved!!!!

+1; Would be nice if there was a period of time for you to recreate the droplet with the same ip.

+1, need to ensure we keep ips. Willing to pay.

A simple Solution if you have sufficient IP. For each hour of IP address not used, Charge them more than the instance itself. Like Amazon. For those having issues with Propagation, use amazon Route 53, it would take effect almost <1min. Compared to rackspace , almost 24 hours.

All the best.

To solve this problem and avoid abuse at the same time, they should implement a system whereby if you have had a droplet that has been paid up for at least 1 month, that IP address will be reserved for a maximum of 2 hours after it's droplet has been deleted. That way, the IP address, once being paid for 1 month, will be reserved only for that customer assuming they create a new droplet after deleting the one it is attached to within 2 hours.

Yes, I had to redeploy my server and their IPs were switched. I had to wait 4 hours for DNS changes to take place.

I think it would be good to have some system like Amazon's Elastic IP.

It the spirit of 'United We Stand, Divided We Fall' let's not dilute, or cannibalize, our votes on this important feature request. A thread similar to this was started almost 1.5 years prior to this one; and, more importantly, has already garnered a whopping 516 votes!

Please transfer your votes to this thread, instead: http://digitalocean.uservoice.com/forums/136585-digital-ocean/suggestions/2993170-movable-ip-from-vm-to-vm-elastic-ip-

probably this one is partially obsolete since Destroy section now has Rebuild option

Agreed! I would like to be able to buy a static IP address and use it with any of my droplets.