I suggest you ...

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.

2,115 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Dries Van DammeDries Van Damme shared this idea  ·   ·  Admin →
    StanStan shared a merged idea: Let users choose the IP address manually or from a stack of IPs  ·   · 

    Edward, our new Director of Customer On Boarding, has been reaching out to a number of customers to see what we can do improve the service. The request to be able to reserve an IP address came up from many customers, and has also received tremendous support from the community with the number of votes that it received on UserVoice.

    As we’ve scaled out the engineering team we have a large number of projects that are currently in traction along with some that we’ve already launched like the new API v2, IPv6, and so forth, but given the huge amount of support for this request, we are going to try and slide this into the roadmap earlier at a higher priority.

    For that we’ll be doing some initial testing to see how we can work this into the existing product set, how much engineering time that will take, and see who on the engineering team can be pulled for this project so that we can ship it sooner.

    As soon as we get out of the planning and architecting phase we’ll move this over to “Started”, which means we’ve begun writing code for this feature.

    Thanks!

    36 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • Gustavo MouraGustavo Moura commented  · 

        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!

      • MorthawtMorthawt commented  · 

        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.

      • Kerem SanKerem San commented  · 

        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.

      • Anonymous commented  · 

        it is very important. +3 votes.

      • Dirk LuijkDirk Luijk commented  · 

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

      • AaronAaron commented  · 

        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.

      • Mark K CowanMark K Cowan commented  · 

        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.

      • Mark K CowanMark K Cowan commented  · 

        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)

      • BenBen commented  · 

        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.

      • JanJan commented  · 

        +3 this is absolutely necessary.

      • Ryan CarrRyan Carr commented  · 

        As Wayne Hartman has mentioned. So this

      • StefanStefan commented  · 

        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)

      • MiracleMiracle commented  · 

        Agree, I will pay money for reserve ip.

      • SaschaSascha commented  · 

        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.

      • Gustavo MouraGustavo Moura commented  · 

        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

      • Alex KinneeAlex Kinnee commented  · 

        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.

      ← Previous 1

      Feedback and Knowledge Base