By default, each Data Mammoth server comes with one public IPv4 address. However, there are scenarios where you may need additional IP addresses — such as hosting multiple SSL-secured websites, running isolated services, or meeting compliance requirements. This guide explains how to request, configure, and manage additional IP addresses.
When You Need Additional IPs
Common reasons for adding extra IP addresses include:
- Multiple websites with dedicated IPs — Some applications or configurations require each website to have its own IP address.
- SSL certificates — While modern servers support SNI (Server Name Indication) for hosting multiple SSL sites on one IP, some legacy clients may require dedicated IPs.
- Service isolation — Run different services (web, mail, database) on separate IP addresses for better organization and security.
- Email reputation — Use a dedicated IP for outgoing email to maintain a clean sending reputation.
- Failover and redundancy — Configure multiple IPs for high-availability setups.
Ordering Additional IP Addresses
Additional IPs are billed as a monthly add-on to your server subscription. The new IP address is typically assigned within a few minutes.
IP Address Limits
There may be a limit on how many additional IPs you can add per server. If you need more IPs than the maximum allowed, contact our support team with a justification for the request.
Configuring Additional IPs on Your Server
After an additional IP is assigned, you need to configure it on the operating system level so your server recognizes and uses it.
Ubuntu / Debian (Netplan)
Modern Ubuntu uses Netplan for network configuration. Edit the Netplan configuration file:
sudo nano /etc/netplan/01-netcfg.yamlAdd the additional IP under the addresses section:
network:
version: 2
ethernets:
eth0:
addresses:
- 203.0.113.10/24
- 203.0.113.11/24
gateway4: 203.0.113.1
nameservers:
addresses:
- 8.8.8.8
- 8.8.4.4Apply the changes:
sudo netplan applyCentOS / AlmaLinux (NetworkManager)
Create a connection profile for the additional IP using nmcli:
sudo nmcli connection modify eth0 +ipv4.addresses "203.0.113.11/24"
sudo nmcli connection up eth0Debian (Traditional ifconfig)
On older Debian systems, edit /etc/network/interfaces:
sudo nano /etc/network/interfacesAdd a virtual interface for the new IP:
auto eth0:1
iface eth0:1 inet static
address 203.0.113.11
netmask 255.255.255.0Restart networking:
sudo systemctl restart networkingVerifying the Configuration
After configuring the additional IP, verify it is active:
# List all IP addresses
ip addr showTest that the IP responds
ping -c 4 203.0.113.11From another machine, try to reach the new IP:
ping 203.0.113.11Configuring Services on Specific IPs
Apache Web Server
To bind Apache virtual hosts to specific IP addresses, edit your virtual host configuration:
<VirtualHost 203.0.113.10:80> ServerName site1.example.com DocumentRoot /var/www/site1 </VirtualHost>
<VirtualHost 203.0.113.11:80> ServerName site2.example.com DocumentRoot /var/www/site2 </VirtualHost>
Nginx Web Server
Bind Nginx server blocks to specific IPs:
server { listen 203.0.113.10:80; server_name site1.example.com; root /var/www/site1; }
server { listen 203.0.113.11:80; server_name site2.example.com; root /var/www/site2; }
Restart the web server after making changes:
# Apache
sudo systemctl restart apache2Nginx
sudo systemctl restart nginxSetting Up DNS for Additional IPs
For each additional IP, create an A record in your DNS configuration:
site1.example.com → 203.0.113.10site2.example.com → 203.0.113.11
Removing an Additional IP
If you no longer need an additional IP address:
Important: Before removing an IP, ensure no critical services, DNS records, or SSL certificates depend on it.
What to Do Next
- Server Networking — IPs, DNS, Reverse DNS — Full networking configuration guide.
- SSL/TLS Certificates — Setup & Renewal — Secure each IP with SSL.
- Managing Server Add-ons — Explore other add-on services.
- Server Firewall Hardening Guide — Secure all your IP addresses.