Multi-IP Dedicated Servers Explained: Performance, Use Cases & Setup

Multi-IP dedicated servers are standard infrastructure for any serious hosting, email, or network operation. Understanding how multiple IPs perform at the network level — and how to configure them correctly — is essential knowledge for any system administrator.

How Multiple IPs Work on a Dedicated Server

When a hosting provider assigns you multiple IPs, they typically come as:

• Individual IPs — each assigned separately, easiest to manage
• IP subnet (/29, /28, /27) — a block of contiguous IPs, better for email and proxy use cases
• Routed subnet — your entire subnet is routed to your server's primary IP, then you manage internal routing

Subnet Size Reference Table

Performance Impact of Multiple IPs

Multiple IPs on a single network interface add negligible overhead. The Linux kernel handles IP aliasing at the kernel level with essentially zero CPU cost. Performance considerations include:

• ARP table size — large subnets (/24+) can create ARP pressure in some datacenter environments
• Connection tracking — each active IP multiplies conntrack table entries proportionally
• Monitoring complexity — more IPs require more monitoring (reputation, blacklists, traffic)

Step-by-Step: Configure Multiple IPs on Ubuntu 24.04

# Method 1: Netplan (recommended for Ubuntu 20.04+)
# /etc/netplan/01-netcfg.yaml

network:
  version: 2
  renderer: networkd
  ethernets:
    ens3:
      dhcp4: no
      addresses:
        - 103.21.58.10/29
        - 103.21.58.11/29
        - 103.21.58.12/29
        - 103.21.58.13/29
        - 103.21.58.14/29
      routes:
        - to: default
          via: 103.21.58.1
      nameservers:
        addresses: [1.1.1.1, 8.8.8.8]

netplan apply

# Verify all IPs are active
ip addr show ens3

# Test connectivity on each IP
for IP in 103.21.58.10 103.21.58.11 103.21.58.12; do
    curl --interface $IP https://api.ipify.org && echo ""
done

Binding Applications to Specific IPs

# Postfix: use specific IP for a virtual domain
/etc/postfix/smtp_reply_filter → smtp_bind_address = 103.21.58.11

# Nginx: listen on specific IP
server {
    listen 103.21.58.12:80;
    server_name site2.yourdomain.com;
}

# Python script: bind to specific source IP
import socket
sock = socket.socket()
sock.bind(("103.21.58.13", 0))
sock.connect(("target.com", 80))

Managing Reverse DNS for All IPs

Each IP used for email or public services should have a valid PTR record. Most hosting providers allow self-service PTR management through their control panel. Best practice naming:

103.21.58.10 → mail1.yourdomain.com
103.21.58.11 → mail2.yourdomain.com
103.21.58.12 → www.yourdomain.com
103.21.58.13 → smtp.yourdomain.com

A /29 subnet with 5 usable IPs is the practical minimum for any serious email operation. It provides enough IP diversity for rotation, warm-up, and isolated sending streams without overcomplicating management.

WebsNP provides /29 and larger subnet allocations on dedicated server plans, with full PTR record management and immediate IP provisioning. View our dedicated server plans or contact sales for subnet pricing.