We see that you are viewing the US version of our website from another country. If you would like to view a local version of our website, please click the link below...

Sales: 1-800-961-2888
Support: 1-800-961-4454
Login
  • MyRackspace Portal
  • Cloud Control Panel
  • Rackspace Webmail Login
Share this on:

Requesting additional IPv4 addresses

Article Id: 1967 | Cloud Servers | Article


Requesting additional IP addresses

Due to the global shortage of IPv4 address space, Rackspace has recently tightened its policies regarding additional IPv4 addresses on Cloud Servers.  We currently only offer additional IPv4 addresses for SSL purposes.  If you wish to obtain an additional IPv4 address, please open a ticket through he Support section of your Rackspace Cloud Control Panel, and please be sure to include the following information:

  • Indicate the hostname name of the server for which you would like to add the IP address. 
  • Please signify acceptance of the additional IP address fee of $2/month per IP address. 
  • Please grant us permission to reboot the Cloud Server so that Cloud Support can configure the IP address.  Please indicate an acceptable maintenance window for us to perform the change, if necessary.  
  • Attach or paste the SSL certificate to the ticket.  The certificate must have been signed by a valid Certificate Authority; self-signed certificates are not accepted.
 
Please note that we cannot allocate more than 4 additional IPv4 addresses to a single Cloud Server.  This gives each Cloud Server a maximum capacity of five (5) IPv4 addresses including the originally assigned public IP address.

 

© 2011-2012 Rackspace US, Inc.

Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License


See license specifics and DISCLAIMER

Comments

Comment: 
What a f...k!! I can understand Your policy, but why $2 per IP per month?!! It was free up to 5 IPs, but now... Maybe later You guys will increase the charge for Your services, who knows?!! I am thinking already go back to Amazon EC2...

Comment: 
Unfortunately what the article says about IPv4 addresses rapidly vanishing worldwide is true. We have a finite number of IPv4 addresses left, so I expect pricing measures like that are intended to encourage people to look for alternatives to using multiple IPv4 addresses. We're still working on IPv6 support for Cloud Servers - once that's available customers will receive large blocks of multiple addresses for no extra charge.

Comment: 

How i can host few sites on one IP? This is impossible for me. No privacy from competitors, no privacy for different businesses, and bad for my SEO strategy. Very bad.

IPv6 is not working on the most internet providers.

Rackspace Comment: 

You should be able to work around privacy and SEO concerns by using different domains pointing to the same IP address. A web server like apache will handle connections according to the domain in the address requested by the browser, so you can use the same IP address for each different domain (called "name-based virtual hosts"). If you use SSL it gets trickier, since certificates are usually based on IP address because of the way browsers have traditionally worked. A tech called "SNI" allows for multiple domains on one IP address with SSL, but only more recent browsers support it.

Comment: 

How much Cloud accounts (another clients) on one IP?

Comment: 

What if i want use nginx on another IP? How professional can work w/o ip addresses?

ross.diaz's picture

Rackspace Comment: 

Hi Maxim,
Please read our article on name-based virtual hosting, here:

http://www.rackspace.com/knowledge_center/node/1900

It has examples for virtual host configurations in both Apache and Nginx. At this time, we can only release additional IPv4 addresses is for SSL. Of course you always get a perfectly good IPv4 address with every server that you build, so you may just want to create an additional server.

Comment: 

NGINX ( Custom compiled after manually installing other packages ) worked great for me with multiples in a single address along side additional IP's.

Comment: 

We have been hosting with Fasthost and after recommendation decided to open a cloud server account with RS. It would have been nice to have been told about the single address before we wasted a week with meetings about the move. We were testing RS with a DNS server first and then possibly moving the hosting of servers but this has made our decision already. bad bad bad....

Rackspace Comment: 

Out of curiosity, why do you require multiple IP addresses to host a DNS server?

Comment: 

We have used rack space cloud servers for both primary and backup name servers for some of our customers. The reason you would need two IP addresses is if you want to use the same server for both primary and backup, which in my experience is not a good idea. The preferable solution is to host you name servers in separate NOCs in separate areas of the country. For example we might have a name server in VA, CA and WA each with different upstream providers.

Comment: 

I realize self-signed certificates are listed as not allowed, but could this policy ever change?

The CA business can be viewed as unneeded/waste of money by some people and organizations and with the start of the Convergence project by Moxie Marlinspike, CA are not needed anymore.

The Convergence project is here:
http://convergence.io

It would be nice if that part of the policy could be re-visited as I do need multiple sockets, specifically for SSL but do not support that industry. I will understand if that policy cannot be revisited, perhaps it's for a variety of reasons you will not accept the certs.

If that ends up being the case, I will have to figure something else out for my projects or the ipv6 rollout or something I suppose.

Rackspace Comment: 

It's a reasonable suggestion, certainly. You might post it to our feature request forum:

http://feedback.rackspacecloud.com/forums/71021-product-feedback

It would be more likely to be seen by decision-makers there, at any rate, than working its way up the chain from here.

If you're going to use Convergence then you can probably also use SNI, though, which would obviate the need for an additional IP address. A user who installs a plug-in for Convergence right now is likely to be using an SNI-compliant browser (newer versions of Firefox and Chrome support it, with the main exceptions right now being IE or Safari running on Windows XP, along with Blackberry and Android default browsers).

http://wiki.apache.org/httpd/NameBasedSSLVHostsWithSNI

Comment: 

Why the limit of 5 to a single server? How can I host multiple websites for SSL purposes?

Rackspace Comment: 

The per-server limit is in place because of the finite availability of IPv4 addresses, I'm afraid. The best approach I can suggest for now would be additional servers for the additional IP addresses. You can try SNI (which allows multiple domains to use SSL on a single IP address), but the limited support for it in IE on Windows XP does make that a less than ideal approach as well.

When IPv6 is available on Cloud Servers there will not be a limit on IPv6 addresses per server.

Comment: 

Something now clearly mentioned is that they're giving an extra IP ONLY FOR SSL purposes!
I was DENIED an extra IP otherwise - and this is the first time it ever happened to me.

I needed one IP for Apache and another IP for a java-based server that also had to run on on port 80. I had this working on other hosts, Rackspace was the only one denying me the IP (even if paying for it!)

Rackspace Comment: 

Out of curiosity, are you running both apache and the app server such that both have to receive external connections, or is apache relaying connections back to the java app server? If the latter, you should be able to bind apache to the external address and the java server to localhost (127.0.0.1), allowing both servers to bind to port 80 without conflict.

Comment: 

Does rackspace support ipv6?
I know with hardware and opensource software should not be a problem.
This way there would be no need for private and public subnets just one complete network of all tcp/ip capable devices of course managed with FW rules. And this would also be a great way to get into ipv6 at least for me.

Rackspace Comment: 

We're still working on getting ipv6 implemented and available on Cloud Servers. The sooner the better, definitely. There is some support for ipv6 in other products (Cloud Sites and Cloud Files, for example), but we're taking some extra time getting Cloud Servers ready.

Comment: 

I currently have 2 linux cloud servers and would like to consolidate it into 1 server only, however I'd need the IP i'm using on the 2nd one to be moved to the 1st. Obviously this means I will incur the cost of $2 for the IP, but was wondering if it would be possible doing something like that.

Rackspace Comment: 

If you're moving the IP address because of an SSL certificate it would probably be approved, as I understand it. For most other reasons you'd probably be encouraged to find a workaround. They've gotten rather strict about extra IP addresses on servers.

Add new comment

©2012 Rackspace, US Inc. About Rackspace | Fanatical Support® | Hosting Solutions | Investors | Careers | Privacy Statement | Website Terms | Sitemap