Version 9 (modified by Jamie McClelland, 13 years ago) (diff)


Allocate dedicated IP address to a member

If a member wants a dedicated IP on one of our shared servers, these are the steps for setting it up.

Tasks that require administrator rights

  • Allocated the IP by editing the ip_allocation page, putting the member domain name next to the next available IP address.

Xen or standalone server

  • Edit the file /etc/network/interfaces on the machine in which the account is hosted. Add a stanza like the following ( is the domain name of hosting order. The Address and netmask should reflect the address and netmask of the record you took from the IP allocation page):
    iface inet static
  • Bring the new IP up with (change to the domain name that you used):
    sudo ifup 


For references, see faq.

  • Add the following files on the vserver host in /etc/vservers/name-of-vserver/interfaces/name-of-interface/
    • dev (eth0, eth1, eth2, etc.)
    • ip
    • prefix (for example, 27 for a /27 address)
  • To make it live without restarting the vserver, run the following on the host (not guest):
    • Add it via ip (change values as needed):
      ip addr add dev eth1
    • Add the ip to the guest's network context (a guests NID is the same as the XID {context ID})
      naddress --add --nid <nid> --ip 
    • Enter the guest and restart any services needing the IP address

Tasks that only require member level permissions

  • Modify the DNS records via the members control panel (DNS service).
    • Change the IP address of the A records to the new IP (usually this would just be, in the example above, and The SSL certificate will typically only apply to these domains - so you don't want to change the IP address of, for example,
  • Add an ssl record to the web config via the members control panel.
    • Under web config, click add new item. Be sure to copy and paste the values from the existing web config rather than taking the default values - you want to be sure to include any extras that you might have added (like the drupal AllowOverride lines).
    • Specify the same login as the owner,
    • Make it enabled,
    • Specify https,
    • For IP address specify the IP address that has been allocated.
    • Finally, add three new lines (Replace chavez with the name of the server the site is hosted on. NOTE: They will need to change these lines after they have purchased an SSL certificate so that they point to their own ssl certificate. These lines are just starters so that it works without an error.)
      #SSL Stuff
      SSLEngine On
      SSLCertificateFile /etc/apache2/ssl/
      SSLCertificateKeyFile /etc/apache2/ssl/