FNF Servers
Log in Sign up
Home Store VPS Dedicated Guides Contact Log in Sign up
  1. Home
  2. Guides
  3. How to Add Your Static IPs

How to Add Your Static IPs

Your Static IP block is routed straight to your server, so every address in it is usable. Add the IPs to your network config on Ubuntu/Debian (netplan or interfaces), Windows Server, then verify.

Updated 2026-08-23

  1. How your Static IPs are delivered

    When you order Static IPs we route the whole block straight to your server. Because the block is static-routed to you rather than sitting on a shared network segment, every address in it is usable — there is no wasted network, broadcast or gateway address to subtract. A /29 gives you 8 usable IPs, a /28 gives you 16, and so on.

    Your server does not know about the extra IPs until you tell it. The steps below add them to your operating system's network configuration so it answers on each address. Pick the section that matches your OS. The examples use documentation ranges (203.0.113.0/24); substitute the real IPs from your welcome email.

  2. Ubuntu / Debian (netplan)

    Recent Ubuntu and Debian releases use netplan. Edit the YAML file under /etc/netplan/ (for example /etc/netplan/00-installer-config.yaml) and add each extra IP under your interface's addresses: list. Add them one per line as /32, or add the whole block in CIDR form:

    network:
  version: 2
  ethernets:
    eth0:
      addresses:
        - 203.0.113.2/24      # your primary IP
        - 203.0.113.10/32     # one extra IP
        - 203.0.113.11/32
        # ...or the whole block in one line:
        - 203.0.113.0/29

    Save the file, then apply it:

    sudo netplan apply

    Check the addresses are now bound:

    ip -br a

    YAML is indentation-sensitive — use spaces, not tabs, and keep each address aligned under addresses:.

  3. Older Debian / Ubuntu (/etc/network/interfaces)

    On systems that still use ifupdown, edit /etc/network/interfaces. The simplest approach is a up ip addr add line per extra IP on your existing interface stanza:

    auto eth0
iface eth0 inet static
    address 203.0.113.2
    netmask 255.255.255.0
    gateway 203.0.113.1
    up ip addr add 203.0.113.10/32 dev eth0
    up ip addr add 203.0.113.11/32 dev eth0

    Alternatively define an aliased interface (eth0:0, eth0:1, ...) per IP. Then restart networking:

    sudo systemctl restart networking

    Verify with ip -br a.

  4. Windows Server

    Open Network & Sharing Center → Change adapter settings, right-click your network adapter and choose Properties. Select Internet Protocol Version 4 (TCP/IPv4), click Properties, then Advanced….

    Under IP addresses, click Add… and enter each extra IP with its subnet mask (for example 203.0.113.10 / 255.255.255.0). Repeat for every address in your block, then click OK back through the dialogs.

    Confirm they are bound from an elevated command prompt:

    ipconfig /all

  5. Verify & troubleshooting

    Confirm the OS now lists every address — ip a on Linux, ipconfig /all on Windows. To test outbound routing from a specific IP:

    ping -I 203.0.113.10 1.1.1.1        # Linux, bind to the source IP
ping -S 203.0.113.10 1.1.1.1        # Windows, -S sets the source

    A freshly added IP can take a minute or two to route as the change propagates — if an address does not respond immediately, wait briefly and try again. If an IP still does not respond after a few minutes, double-check the address and mask match your welcome email, then open a ticket and we will confirm the route on our side.

See plans Ask a question