Ordering additional IPv4 addresses for your VPS

Need a second (or third, fourth) IPv4 address on an existing LYLIX VPS? This article covers how to order them, what justification we need, and what to do with the IP once it lands.

Why we ask for justification

IPv4 is exhausted globally. ARIN (the regional registry) issues new addresses to providers based on documented utilization. To keep our allocation valid we have to attach a use case to each IP we hand out — and we get audited on this. Standard justifications:

• Multiple SSL/TLS certificates for distinct domains on the same VPS (less common now thanks to SNI but still legitimate for specific TLS-terminating appliances).
• Multi-tenant PBX with separate IPs per carrier or per customer for SIP signaling.
• Outbound mail separation — dedicated IP for transactional mail vs marketing vs in-app.
• Service isolation — multiple services that must bind to different IPs for compliance or carrier requirements.
• Public-facing test/staging environments — separate IP for staging.

"I'd just like an extra one" doesn't pass ARIN review. If your reason isn't on the list above, mention what you actually need it for — we'll let you know if it works.

Ordering

1. Log in to the portal.
2. Open a ticket in the Virtual Private Server department titled "Additional IPv4 request — <hostname>."
3. Include:
   • Number of additional IPs needed.
   • Justification (one to two sentences).
   • Whether you need contiguous (e.g., a /29 block) or any-available.
   • Whether you need rDNS set at the same time, and what the desired PTR is.
4. We'll respond with pricing (additional IPs are billable per IP per month) and proceed if approved.

Pricing

Additional IPv4 addresses are billed per IP per month, proratable. Pricing tier depends on volume and current ARIN pressure — we'll quote on the ticket. IPv6 is free in any quantity (you'd be surprised how often we still need to mention that).

What you get back

The ticket reply contains the additional IP address(es) and the netmask for your VPS. You add the IP to your VPS's network configuration:

# Debian/Ubuntu — modify /etc/netplan/01-netcfg.yaml
network:
  ethernets:
    eth0:
      addresses:
        - <primary-ip>/24
        - <additional-ip>/24
  version: 2

netplan apply

# AlmaLinux/Rocky — modify the connection profile
nmcli con mod <conn-name> +ipv4.addresses <additional-ip>/24
nmcli con up <conn-name>

Then verify:

ip addr show eth0
ping -c 1 -I <additional-ip> 8.8.8.8

Setting reverse DNS

By default the new IP has a generic LYLIX rDNS. To set a custom PTR (required for sending mail), use the portal's Reverse DNS tab on your VPS. See Setting reverse DNS (PTR).

Returning an IP

If you no longer need an additional IP, open a ticket requesting we release it. Billing stops on the next cycle. We do recycle returned IPs — flag in advance if the returned IP needs to be quarantined for blacklist cooldown rather than reissued.