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.
-
Dries Van Damme
- Sep 11 2018
- Future consideration
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +1834
Related ideas
I total agreed this feature is important due to the limitation of droplet downgrade. It could either coverted to floating IP or transfer to the new droplet.
Attachments Open full size
Why is this not solved by the floating IPs?? I do not get what this issue exactly requests.
Attachments Open full size
Seriously need this feature. Floating IPs is not a solution for this. Many of us use VPN's for securing our infra with whitelisting IP addresses.
Attachments Open full size
How is this still a problem after all the years it's been requested.
Attachments Open full size
use floating IP address, this idea is not good
Attachments Open full size
How does the Floating IP feature not cover this?
Attachments Open full size
Just use float IP or the load balancer (it comes with a static ip)
Attachments Open full size
What it comes down to is the use of floating IPs and rDNS records it seems. Reverse DNS lookup only points to the droplet IP, which of course means that all mail from the server/droplet will likely get spammed, even with proper SPF, DKIM and DMARC setup. Currently you can't seem to have both worlds - floating IPs for juggling droplets AND email deliverability via rDNS on the floating IP. The email looks like it's coming from a different domain than the FQDN.
Attachments Open full size
It's a pain really. I've just accidentally destroyed my droplet while I'm going to rebuild it (because destroy and rebuild are in the same menu). And I lost my IP. Been 5 days trying to get my IP back by creating-destroying droplets, no luck so far. (The result of pinging the IP is still RTO - hoping it's still unassigned to some other droplet)
Attachments Open full size
Floating IPs are not a solution for those of us who need PTR records. They’re also not a solution to the problem of needing to retain existing anchor/permanent IPs. This has been holding up using DO at work. We stick to AWS, in big part, because of this feature. It’s also a personal annoyance.
Attachments Open full size
Agreed! I would like to be able to buy a static IP address and use it with any of my droplets.
Attachments Open full size
probably this one is partially obsolete since Destroy section now has Rebuild option
Attachments Open full size
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-
Attachments Open full size
I think it would be good to have some system like Amazon's Elastic IP.
Attachments Open full size
Yes, I had to redeploy my server and their IPs were switched. I had to wait 4 hours for DNS changes to take place.
Attachments Open full size
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.
Attachments Open full size
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.
Attachments Open full size
+1, need to ensure we keep ips. Willing to pay.
Attachments Open full size
+1; Would be nice if there was a period of time for you to recreate the droplet with the same ip.
Attachments Open full size
+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!!!!
Attachments Open full size