14 comments

Add a comment…

Sign in

prestine

Your email address

Check!

invalid email

(thinking…)

Reset

or sign in with

• 
• 

UserVoice password

Forgot password?

Create a password

Your name

I agree to the terms of service

You'll receive a confirmation email with a link to create a password (optional).

Signed in as (Sign out)

Close

Close

Post comment Submitting...

• Justin Wilson commented  ·  May 14, 2012 21:01  ·  Flag as inappropriate  ·  Delete

  I hope Rackspace does do this as it would be VERY helpful and useful for my business. Rackspace, acgann made a good point so if you want, you could setup some kind of limit like.. automatically releases in say 30 days if not used. :)

• Kevin Veroneau commented  ·  December 23, 2011 08:28  ·  Flag as inappropriate  ·  Delete

  I agree with acgann, being able to deploy a server without a public IP address which is only on servicenet. As long as you have one server with a public IP address, you can easily access the other servicenet-only servers via SSH/PowerShell/RDP.

• Jarl Friis commented  ·  October 12, 2011 11:48  ·  Flag as inappropriate  ·  Delete

  Seems like a duplicate of this one:
  http://feedback.rackspacecloud.com/forums/71021-product-feedback/suggestions/998625-configurable-ip-addresses

• acgann commented  ·  August 24, 2011 09:06  ·  Flag as inappropriate  ·  Delete

  You know, we have 20+ servers and they are all behind the firewall. Most don't actually need public IPs. Now if Rackspace wanted to increase flexibility, they'd let us spin up servers that are "servicenet only" that ONLY have a private IP. And then they could let us use the ones we would've gotten anyway in the pool.

• acgann commented  ·  July 13, 2011 08:49  ·  Flag as inappropriate  ·  Delete

  Considering the crunch of IPv4, this probably won't come soon. No way are they going to let people hold on to IPs they aren't actively using.

  They may be able to do it for IPv6 though.

• Matt commented  ·  June 09, 2011 18:30  ·  Flag as inappropriate  ·  Delete

  Moving an IP to a different image or load balancer would be awesome. We're gonna need this one soon! Not to mention the peace of mind that you are have control over an IP since we have so many things pointing to it.

• gpasat commented  ·  May 27, 2011 21:12  ·  Flag as inappropriate  ·  Delete

  Another great feature that AWS has on top of RS

• Jeffrey Nichols commented  ·  May 17, 2011 06:26  ·  Flag as inappropriate  ·  Delete

  I require this feature in Cloud Sites so that not all of my sites have the same IP. However, it's my fault for not checking for this feature before I started moving all my sites there.

• Lawrence commented  ·  March 16, 2011 08:37  ·  Flag as inappropriate  ·  Delete

  It surely would save a lot of hassles and DNS reconfiguration at the time of deploying a new production server based on an existing development server or image. Even a few hours IP reservation between server deletion and creation would do in most cases.

  Voted.

• Dimas commented  ·  March 08, 2011 09:06  ·  Flag as inappropriate  ·  Delete

  Ditto!

• graytech commented  ·  February 23, 2011 16:00  ·  Flag as inappropriate  ·  Delete

  I would like to request this as well. It seems that every time I get a new IP address on a new instance in the cloud, the IP address ends up listed on an RBL somewhere. Every time, this happens I have to go through all sorts of contortions to get it removed. If I had a reserved and configurable IP address (like AWS) I would only have to worry about it and avoid the problems with RBLs that come up during migration.

  In an effort to address this issue, maybe RS can setup one dedicated ip address per account or pull such request from a set of reserved ip blocks to be used for just such purposes. This way they can decrease the problems caused by spammers use of "throw away" IP addresses in the cloud.

• getnrdone commented  ·  February 02, 2011 13:34  ·  Flag as inappropriate  ·  Delete

  This can come in very handy. Currently i have a test lab on rackspace that I only use a couple times a week. To save money i delete the machines and restore when i need them (since there is not suspend option). When i do i loose the static addresses assigned every time. This causes all sorts of issues with the domain controllers and citrix machines that point to IP's for certain things. At the very least I would love to have a block of internal IP's assigned to my account that i can reuse and assign as needed.

• Brian Gallagher commented  ·  February 01, 2011 03:39  ·  Flag as inappropriate  ·  Delete

  It would be very handy when testing / switching between different virtual server configurations. And being able to retain an IP address for a suspended server would be very helpful.

• TechSmart commented  ·  November 02, 2010 08:55  ·  Flag as inappropriate  ·  Delete

  This will be even more important with the release of IPv6. Having a /56 for each server is not as valuable as having a /56 per account.