DO Ideas 2

movable IP from VM to VM ("elastic IP")

It would be great to be able to have IPs we could move from VM to VM. Just like say, Amazon's "elastic IP".

  • Jean-Philippe Boily
  • Sep 11 2018
  • Shipped
  • Sep 11, 2018

    Admin Response

    Hey All, Floating IPs has gone live today. Head over to our blog (https://www.digitalocean.com/company/blog/floating-ips-start-architecting-your-applications-for-high-availability/) and check out the community tutorials (https://www.digitalocean.com/community/tags/high-availability?type=tutorials) to get started.
  • Attach files
  • Anonymous commented
    September 11, 2018 19:56

    Yes, it is useful feature, which will keep me staying with Digital OCean after free trial, for sure!

  • Sylwester Lachiewicz commented
    September 11, 2018 19:56

    great - i would like to convert my public droplet IP to floating (and later release others droplet public ip)

  • Vishal Doshi commented
    September 11, 2018 19:56

    YAY!!! Thank you

  • Eric commented
    September 11, 2018 19:56

    AWESOME!!!!

  • Balazs Nadasdi commented
    September 11, 2018 19:56

    Awesome news! =D Thank you.

  • Rick Nguyen commented
    September 11, 2018 19:56

    That's awesome! Can't wait.

  • Jean-Philippe Boily commented
    September 11, 2018 19:56

    Yay! Glad that what I shared 3 years ago is now in the pipeline! :D

  • Leo Winter commented
    September 11, 2018 19:56

    Nice!

  • Eric commented
    September 11, 2018 19:56

    Wonderful!!!!!!!!!!!!

  • Anonymous commented
    September 11, 2018 19:56

    this is great news :)

  • Daniel Kelly commented
    September 11, 2018 19:56

    Yusssssss

  • Andy Smith commented
    September 11, 2018 19:56

    BOOOOOOOOMMMM TTTOOOOWWWWNNNNNNN!

  • Paul commented
    September 11, 2018 19:56

    Yes!

  • TundraWare Inc. commented
    September 11, 2018 19:56

    +1

    This would go a long way to helping us do hot-cold DR failovers.

    It would also be nice to be able to multihome a droplet with several IPs.

  • Anonymous commented
    September 11, 2018 19:56

    I came across this with the "heartbeat" software. EasyDNS has a service to do fail-over. Maybe that capability could be added to the DO DNS subsystem. At the end of the day, 24x7 services are hear to stay. There are multiple ways to implement the fail-over. I am hoping there is at least one way to implement failover of the DNS/Load balancer at Digital Ocean.

  • Chad - Bible Us commented
    September 11, 2018 19:56

    +1, but we need the price to remain the same. I think the ip changing on you is the only big draw back to DO at this point. next is better monitoring and explanation of billing, i know people looking to use it for VOIP have concerns about consistency and billings. see nerd vittles.

    also i saw this option for dynamic dns: https://www.digitalocean.com/community/questions/can-i-reserve-a-specific-ip-address
    You can use a service as DynDNS to get a domain for your droplet. If you then install ddclient on that droplet, the domain will always point to the correct IP, even if it changes after you e.g. restore the droplet from a snapshot.

  • Daniel Landers commented
    September 11, 2018 19:56

    +1 this is stopping our organisation moving our entire hosting to digital ocean

  • Nicolae Serban commented
    September 11, 2018 19:56

    This is extremely helpful for managing load balancer servers.

    +1

  • Joel commented
    September 11, 2018 19:56

    +3

  • Eric commented
    September 11, 2018 19:56

    DO, please implement this feature.

    Linode does this well with their IP failover IP option. https://www.linode.com/docs/networking/remote-access.

  • Maxym commented
    September 11, 2018 19:56

    Ability pick the IP for my droplets would be an absolutely awesome feature! This way, I can make a truly reliable setup.

  • Tri-net Solutions commented
    September 11, 2018 19:56

    Good idea.

  • Sergey commented
    September 11, 2018 19:56

    Is there any indication when this feature will be released? It is extremely useful one...

  • Fernando Aleman commented
    September 11, 2018 19:56

    3 votes for this feature. This is really the only thing preventing me from moving over from AWS.

  • Anonymous commented
    September 11, 2018 19:56

    This is extremely helpful for managing load balancer servers.

    Without this, a technical issue regarding DNS can take up to 24 hours to solve.

  • Eric commented
    September 11, 2018 19:56

    Linode does this well with their IP failover IP option. https://www.linode.com/docs/networking/remote-access. This really is the last thing I need in order to have a truly high availability server configuration.

    Along with their IP swap feature Linode is giving DO a run for their money now that Linode has copied DO pricing.

  • David Farrell commented
    September 11, 2018 19:56

    The way I see it, this idea would work very well if an IP was assigned to an account for each monthly-prepaid droplet or for each droplet that has existed for longer than one month. This would allow an IP to be reserved immediately but also for an IP to be reserved by accounts wishing to be charged per hour, and would also eliminate potential misuse by users who want to create and destroy loads of droplets just to saturate the IP pool.

  • ld commented
    September 11, 2018 19:56

    This is the only reason for my reluctance to deploy on DO. We really need support for reserved IP - even if it's for the short period of time (for example, drop droplet, create a new one in 10 minutes or within 1 hour, but definitely get the same IP). Without this I am afraid DO will only work for short term reservations for us.

  • Pierre-Louis Gottfrois commented
    September 11, 2018 19:56

    Any new on this ?

  • Kim Full commented
    September 11, 2018 19:56

    MUST !!!!

  • Anonymous commented
    September 11, 2018 19:56

    I hope it is realized that elastic IP addresses are a large increase in the statefulness of DigitalOcean's setup and costs more because more IP addresses effectively will be in use and IPv4 addresses are scarce these days. So while it has a lot of support it will take quite some effort on their part.

  • Víctor M. Cuadrado commented
    September 11, 2018 19:56

    are we there yet?

  • Anonymous commented
    September 11, 2018 19:56

    I'm all for this feature.

  • Daniel Hemmerich commented
    September 11, 2018 19:56

    yes

  • Jon commented
    September 11, 2018 19:56

    +3

  • Dan commented
    September 11, 2018 19:56

    Need this feature.

  • Anonymous commented
    September 11, 2018 19:56

    Just signed up. Any update on this?

  • Anonymous commented
    September 11, 2018 19:56

    Not having this is a deal breaker for me. Can move today from AWS.

  • Daniel Kelly commented
    September 11, 2018 19:56

    Ya hiiii, if someone from DO could go ahead and give us an update that would be greeeaaaat... kayy??

  • Nathan commented
    September 11, 2018 19:56

    Come on 2 years after this started and with 1386. The feature still not there yet ?

  • Abraham Godong commented
    September 11, 2018 19:56

    +3

  • Kelvin Luck commented
    September 11, 2018 19:56

    +1

  • Anton commented
    September 11, 2018 19:56

    I'm evaluating cloud hosts for some systems we're migrating. Lack of this feature alone forces me to pretty much reject Digital Ocean. All the other companies we're looking at support reserved IPs that won't ever disappear along with a VM instance.

  • Eric commented
    September 11, 2018 19:56

    +3. I'm still interested in this as it would make HA configuration much easier.

  • Nicholas Rempel commented
    September 11, 2018 19:56

    Yes please!

  • Thomas Sileo commented
    September 11, 2018 19:56

    +1

  • Relvao commented
    September 11, 2018 19:56

    +1

  • Anonymous commented
    September 11, 2018 19:56

    Can't use DO without this feature

  • Anonymous commented
    September 11, 2018 19:56

    Really Really important. This is why I can't move a lot of my box from aws to DO

  • Anonymous commented
    September 11, 2018 19:56

    + 100000 please, make this possible, at least for Public IP's. Local networking should be the same as well.

  • Doug Stanley commented
    September 11, 2018 19:56

    +3

  • joris commented
    September 11, 2018 19:56

    +3... A must have...

  • Fox Chao commented
    September 11, 2018 19:56

    I vote for this feature

  • Anonymous commented
    September 11, 2018 19:56

    This is currently a barrier to entry for me hosting my email on a droplet. I would LOVE this feature.

  • Anton Taraev commented
    September 11, 2018 19:56

    +1

  • Laszlo Török commented
    September 11, 2018 19:56

    +1

  • Ben commented
    September 11, 2018 19:56

    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.

  • Matt commented
    September 11, 2018 19:56

    Please! This has to be done! Why has this been marked as "PLANNED" for over a year with no update?

  • YtJ commented
    September 11, 2018 19:56

    +1

  • Al commented
    September 11, 2018 19:56

    This feature would be great. Server upgrades should work smoother with an elastic IP and without downtime. You can assign for example the IP to a backup server, upgrade the main server and then reasign the IP to the main server. Great idea.

  • Kresimir Pendic commented
    September 11, 2018 19:56

    +1 that is very cool feature,, please add this do! thanks!

  • Nirbhab Barat commented
    September 11, 2018 19:56

    +3

  • Anonymous commented
    September 11, 2018 19:56

    Elastic IP is something that AWS got completely right. DigitalOcean will kick AWS' ass if something similar is implemented.

  • Alexei Boronine commented
    September 11, 2018 19:56

    +1. This is an absolutely essential feature. The only way I imagine doing this right now is having a dedicated proxy droplet. Swapping out IPs though DNS will not work safely for anything but the most trivial static sites.

  • Ihor Vorotnov commented
    September 11, 2018 19:56

    +2 for this.

  • A commented
    September 11, 2018 19:56

    the only thing stopping me from going to DO ... please add this

  • Anonymous commented
    September 11, 2018 19:56

    +1

  • Danielle commented
    September 11, 2018 19:56

    +20

  • Ben commented
    September 11, 2018 19:56

    +1

  • Anonymous commented
    September 11, 2018 19:56

    +1

  • Anonymous commented
    September 11, 2018 19:56

    +1

  • xandros commented
    September 11, 2018 19:56

    +1

  • Jean-Philippe Boily commented
    September 11, 2018 19:56

    @Wouter: haha, this is exactly what I had in mind! :P

    I guess things will accelerate from now on, which is awesome! More good stuff coming in the next few months I guess.

  • Wouter van Lent commented
    September 11, 2018 19:56

    So with the new investment this is gonna be a piece of cake, right? ;-) Any updates?

  • agius commented
    September 11, 2018 19:56

    I would rather use DO than AWS, but I need to run an email cluster. This feature is a must-have for running your own email.

  • Niels Wind commented
    September 11, 2018 19:56

    +1

  • Hans commented
    September 11, 2018 19:56

    Agree with all comments below. It is annoying that there is no option for a static and/or "elastic IP"

  • Salvatore commented
    September 11, 2018 19:56

    There is another idea ("Make sure we can keep an IP if we recreate a droplet.") with almost 800 votes too, that could also be solved with "elastic IPs". So this is near 1600 votes right now. Come on, this would be a really good feature!!

  • Robert Schwandner commented
    September 11, 2018 19:56

    +1

  • Timothy Anderson commented
    September 11, 2018 19:56

    +1.

  • Charles Ricketts commented
    September 11, 2018 19:56

    +1 Any updated status on this?

  • Sushant gupta commented
    September 11, 2018 19:56

    Desperately need Elastic IP. Had it been supported I would have migrated today from AWS.

  • Ka‘a Kihe commented
    September 11, 2018 19:56

    +1

  • Chris commented
    September 11, 2018 19:56

    Yes voted. I really need this feature.

  • Cyril Nicodème commented
    September 11, 2018 19:56

    It's been 8 month since these feature has been marked to planned (If I understand correctly), is there any new evolution regarding this ! I'd really need this feature.

    Thanks

  • Nicholas Garofalo commented
    September 11, 2018 19:56

    Like many others, this is the sole feature preventing us from moving any production servers to DO. :(

  • Laszlo Török commented
    September 11, 2018 19:56

    +1

  • Paul commented
    September 11, 2018 19:56

    Elastic IP is a must service, so a big +1 from me. Having moved from AWS this is one the features I really miss.

  • Michael van Rooijen commented
    September 11, 2018 19:56

    It would be nice to have an ip which you can freely assign to any VM. This'd be great in case your load balancer VM goes down and you want to quickly boot up a new VM with for example a backup image and assign the original load balancer's IP to the new load balancer for minimal downtime. The chances of a VM going down, and it being your load balancer are fairly slim, but in the event that it does happen, this'd be great.

  • Anonymous commented
    September 11, 2018 19:56

    i++

  • Anonymous commented
    September 11, 2018 19:56

    +1

  • Adam commented
    September 11, 2018 19:56

    +1
    I think the service and platform are great, I want to move more resources from amazon aws to digital ocean, but I need to ensure the IP doesn't change. I can manage this to an extent with short TTL on my dns records but I cannot take the chance with a customer that their domain would magically be pointing to another site... imagine that phone call.

  • Pavel Vasev commented
    September 11, 2018 19:56

    +100 because this is vital. For example we have > 10 DNS servers for various domains. The change of IP address is critical to our customers and we do that in many steps.
    So we must be absolutely sure that certain IP address tied to us whenever any VMs we use. And also we need to move IP address from one VM to another sometimes (e.g. when upgrading or hot-switching frontends).

    Now we use Amazon Elastic IP. And we need the same in Digital Ocean to switch in,

  • Pavel Vasev commented
    September 11, 2018 19:56

    +100

  • Satish commented
    September 11, 2018 19:56

    Really need this feature.

  • a.kamel@vireton.com commented
    September 11, 2018 19:56

    +3

  • Picharras commented
    September 11, 2018 19:56

    +1

  • Ruslan Pashkoff commented
    September 11, 2018 19:56

    +1

  • Nuno Barreto commented
    September 11, 2018 19:56

    This is a major problem. I have just recreated 5 servers and none of them kept the public ips, and only one kept the private ip. Not fun at all :(

  • Ruud commented
    September 11, 2018 19:56

    I think this is a necessary feature because we don't want to rely on dns changes.

  • Daniel Norton commented
    September 11, 2018 19:56

    ++

  • Bruno Nielsen commented
    September 11, 2018 19:56

    +1

    I Agree

  • Marcos Piccinini commented
    September 11, 2018 19:56

    +1 only thing keeping me from moving a big project. It's really lame!

  • Ben Oman commented
    September 11, 2018 19:56

    +1

  • Anonymous commented
    September 11, 2018 19:56

    +1

  • Adin commented
    September 11, 2018 19:56

    Any idea when this is planned for?

  • Adin commented
    September 11, 2018 19:56

    +1

  • Pablo commented
    September 11, 2018 19:56

    The likelihood of having 'elastic IPs' adopted will increase if folks consolidate their votes. To that end, vote for this suggestion (which essentially accomplishes the same objective), instead: https://digitalocean.uservoice.com/forums/136585-digital-ocean/suggestions/2993170-movable-ip-from-vm-to-vm-elastic-ip- (and has already accumulated 455 votes!)

  • Michele Cantelli commented
    September 11, 2018 19:56

    +1

  • Michele Bursi commented
    September 11, 2018 19:56

    +1, it would be so useful!

  • Vladymyr Protsenko commented
    September 11, 2018 19:56

    +1

  • Blaine Haun commented
    September 11, 2018 19:56

    +3

  • Greg Edwards commented
    September 11, 2018 19:56

    +1

  • Vineet Joshi commented
    September 11, 2018 19:56

    I need this before I can move my production environment to Digital Ocean.

  • Holger Wiehen commented
    September 11, 2018 19:56

    +1 Needed

  • Jamie commented
    September 11, 2018 19:56

    Please add this. thanks

  • Anonymous commented
    September 11, 2018 19:56

    It would be helpful to know that if we resized a droplet we could guarantee the IP address would not change. Eg. IP address remains allocated to account for n hours after droplet terminated.

  • Ash commented
    September 11, 2018 19:56

    I could really do with this for my next project too!

  • Aidan commented
    September 11, 2018 19:56

    When will this become available, i need this now.

  • Brian commented
    September 11, 2018 19:56

    I really need this feature, in fact I was referred to this thread after I posted the same thing:

    https://www.digitalocean.com/community/questions/can-i-reserve-a-specific-ip-address

  • Jason Parraga commented
    September 11, 2018 19:56

    DO really needs this

  • Nick Walke commented
    September 11, 2018 19:56

    This needs to happen before DO is viable for companies that care about uptime.

  • Luis Muñoz commented
    September 11, 2018 19:56

    Moisley, as an additional note, having the persistent IP --> droplet mapping managed by DigitalOcean improves reliability and likely, provides a new billable product for DO.

  • Luis Muñoz commented
    September 11, 2018 19:56

    Moisey, yes. There are use cases where having an IP address that can be assigned to specific instances is desirable.

    Think about hosting a DNS server farm. For this use case, each authoritative name server needs to have a fixed IP address. In case of a failure or rebuild, the persistent IP address could be applied to another (replacement? upgraded? reconfigured?) server quickly.

    Your domain registrar records would remain unchanged, yet you would be able to replace / relocate servers transparently without having to modify hundreds of thousands of DNS zone delegations.

  • Euan Jonker commented
    September 11, 2018 19:56

    This is the one thing that will make me move from AWS to DO.

  • Kenn Ejima commented
    September 11, 2018 19:56

    Right now, we're taking the risk of using DO without this feature - when the master nginx goes down, we process failover, write a ticket to move the IP and hope it be executed by DO staff in a few minutes in the middle of Christmas dinner. (seriously, gaming apps have high traffic in those seasons...)

    So far DO staff is responsive and good, and it sure mitigates my worries, but this feature would *remove* my worries.

  • Moisey Uretsky commented
    September 11, 2018 19:56

    The way we use "Planned" is to indicate that we will be actively working to implement the suggestion.

    It usually means that it's either in the planning and discussion phase, or it's being scheduled into the roadmap.

    Once we start actual development of the feature the flag for the topic will be changed to started to indicate that we are now actively developing the new feature.

    Thanks

  • Vincent van Megen commented
    September 11, 2018 19:56

    This has been marked as planned, can you tell us more?

  • Benjamin Vetter commented
    September 11, 2018 19:56

    i think so too: a load balancing layer is imho no replacement for elastic ips.

    my preferred solution would be being able to re-route an elastic ip to any of my droplets via an api request (like aws or hetzner).
    second choice would be a solution where an elastic ip could be brought up on any of my droplets (like linode).

  • Trevor Kensiski commented
    September 11, 2018 19:56

    In regards to your response Moisey, I would rather have the floating IP than a load balancing application, I have uses to be running my own HA proxy (or similar proxy applications) that do load balancing.

  • Moisey Uretsky commented
    September 11, 2018 19:56

    We will be looking into providing this feature either directly or through a load balancing application layer but too early for a planned ETA just yet.

    Thanks

  • Vincent van Megen commented
    September 11, 2018 19:56

    Any plans for this? Really need this for my app!

  • Anonymous commented
    September 11, 2018 19:56

    would love to see this

  • Moisey Uretsky commented
    September 11, 2018 19:56

    You can resize the server and we are just about finished with the code updates to the resize that also does a migrate onto a new hypervisor and in every resize your IP would be preserved.

    If you want to add one more layer to this you can also setup nginx on a small server and have it act as a reverse proxy then you have full control over which domain to point to which server.

    This way you can have 50 websites on a single server and if one of them grows large you can use nginx to reverse proxy that to a different server moving it to it's own virtual server which is larger without the need to contact the customer for any DNS updates.

  • Jeremy Price commented
    September 11, 2018 19:56

    build new server to replace old server... would i rather a) swap the IP from the old to the new server for (near instant) happiness or b) go through DNS rigamorole as noted above _and_ have to keep both running for days to account for ISPs who ignore low TTLs?

  • Benjamin Vetter commented
    September 11, 2018 19:56

    This is the only single feature preventing me from moving to digital ocean.

  • Moisey Uretsky commented
    September 11, 2018 19:56

    The IP is yours as long as you have the virtual server and you can also rebuild the server if necessary and retain the IP, the only time you really lose it is if you destroy the server.

    Is there any case in which the server would be destroyed since that is what would cause the issue?

  • John Daniels commented
    September 11, 2018 19:56

    This, or 'floating IP addresses' are essential for failover-style HA.

  • Ferenc Szalkai commented
    September 11, 2018 19:56

    Agree!

  • Dash Bitla commented
    September 11, 2018 19:56

    This will be a great feature and also helps for HA Setups. Swap IPs would help too.

  • luis acevedo commented
    September 11, 2018 19:56

    Agreed :D