• November 10, 2025

How to Configure Multiple Public IPv4 Addresses on a Vultr Compute Instance

How to Configure Multiple Public IPv4 Addresses on a Vultr Compute Instance

Learn how to assign and configure multiple public IPv4 addresses on Vultr Compute Instances for Ubuntu, CentOS, FreeBSD, and Windows.

Assigning multiple public IP addresses to a Vultr Compute Instance allows you to host multiple services, bind applications to separate IPs, or configure advanced networking setups such as NAT or IP-based virtual hosts. Vultr makes it easy to add and manage additional IP addresses through the Vultr Customer Portal.

This guide explains how to assign and configure multiple public IPv4 addresses on a Vultr Compute Instance. It covers adding IPs from the portal, configuring the operating system, and verifying network connectivity.

Prerequisites

Before you begin, you need to:

  • Have access to Vultr Customer Portal.
Configure multiple public IPv4 addresses on Ubuntu

Follow these steps to assign and configure multiple public IPv4 addresses on your Ubuntu instance.

  1. Log in to the Vultr Customer Portal.
  2. Navigate to Compute under the Products section.
  3. Select your Ubuntu server and click Settings.
  4. Under the IPv4 section, you can see the default IP address assigned to the server.
  5. Click Add Another IPv4 Address, check the box labeled Yes, add and restart this server, and click Add IPv4 Address to assign a new IPv4 address to your server.
  6. After the IP is assigned, you must manually configure it on the server.
  7. Click Network Configuration to generate and copy the custom Netplan template based on your OS.
  8. Below is an example configuration for Ubuntu server using Netplan.
    yaml
    network:
      version: 2
      renderer: networkd
      ethernets:
        enp1s0:
          dhcp4: no
          addresses: [192.0.0.4/23,192.0.2.5/32]
          nameservers:
            addresses: [192.0.0.6]
          routes:
          - to: default
            via: 192.0.0.1
          - to: 169.254.0.0/16
            via: 192.0.0.1
            metric: 100

    Replace the following values with those provided in your Vultr Customer Portal:

    • 192.0.2.5: Your newly assigned IPv4 address.
    • 192.0.0.6: Your DNS server.
    • 192.0.0.1: Your gateway IP.

    In the above configuration:

    • network: The top-level key that begins the Netplan configuration
    • version: Specifies the Netplan format version. Version 2 is the standard used in most modern Ubuntu systems.
    • renderer: Indicates which backend to use for applying the configuration.
    • ethernets: Defines Ethernet interface configurations. All Ethernet-based interfaces should be declared under this section.
    • enp1s0: The name of the network interface being configured.
    • dhcp4: no: Disables DHCP for IPv4, so the interface uses a static IP configuration.
    • addresses: A list of static IP addresses assigned to the interface.
    • nameservers: Specifies DNS resolver addresses.
    • routes: Adds static routes to control traffic flow.
    • to: default / via: 192.0.0.1: Sets the default gateway to 192.0.0.1, used for routing external traffic.
    • to: 169.254.0.0/16 / via: 192.0.0.1 / metric: 100: Routes link-local addresses via the same gateway with a metric of 100.
  9. After you have copied the configuration, SSH into your Ubuntu server.
  10. Create a new Netplan configuration file using a text editor such as nano.
    console
    $ sudo nano /etc/netplan/10-enp1s0.yaml
  11. Paste the copied configuration into the file, then save and exit.
  12. Set restrictive file permissions to prevent unauthorized changes.
    console
    $ sudo chmod 400 /etc/netplan/10-enp1s0.yaml
  13. Test the configuration before applying it permanently.
    console
    $ sudo netplan try

    This command applies the new network configuration temporarily and gives you 120 seconds to confirm that everything is working as expected. If the system loses connectivity or something goes wrong, Netplan automatically rolls back to the previous configuration after the timeout, preventing accidental lockouts on remote systems.

    • Press <kbd class=”key”>Enter</kbd> to accept and apply the changes permanently.
    • Press <kbd class=”key”>Esc</kbd> or wait for the timer to expire if something breaks.
  14. If everything works as expected, apply the configuration permanently.
    console
    $ sudo netplan apply
  15. Restart the server from the Vultr Customer Portal by clicking the Server Restart icon to make the changes take effect.
Configure multiple public IPv4 addresses on  CentOS

Follow these steps to assign and configure multiple public IPv4 addresses on your CentOS instance.

  1. Log in to the Vultr Customer Portal.
  2. Navigate to Compute under the Products section.
  3. Select your CentOS instance from the list.
  4. Click the Settings tab.
  5. Under the IPv4 section, you can see the default IP address assigned to the server.
  6. Click Add Another IPv4 Address.
  7. Check the box labeled Yes, add and restart this server, then click Add IPv4 Address to assign a new IP.
  8. After the IP is provisioned, click the Server Restart icon to reboot the instance.
  9. On boot, cloud-init will automatically configure the newly assigned IP address in the network interface.
Note

If the new IP address is not automatically configured, navigate to the Network Configuration section in the portal and follow the manual steps provided for your operating system.

Follow these steps to assign and configure multiple public IPv4 addresses on your FreeBSD instance.

  1. Log in to the Vultr Customer Portal.
  2. Navigate to Compute under the Products section.
  3. Select your FreeBSD instance from the list.
  4. Click the Settings tab.
  5. Under the IPv4 section, you can see the default IP address assigned to the server.
  6. Click Add Another IPv4 Address.
  7. Check the box labeled Yes, add and restart this server, then click Add IPv4 Address to assign a new IP.
  8. SSH into the server.
  9. Create a backup of existing /etc/rc.conf.
    console
    $ sudo cp -pvr /etc/rc.conf /etc/rc.conf.backup
  10. Edit the /etc/rc.conf file and update it with the following configuration.
    ini
    hostname="FreeBSD"
    sshd_enable="YES"
    ntpd_enable="YES"
    static_routes="linklocal"
    route_linklocal="-net 169.254.0.0/16 -interface vtnet0"
    ifconfig_vtnet0="inet 192.0.0.4 netmask 255.255.254.0"
    defaultrouter="192.0.0.1"
    ifconfig_vtnet0_alias0="192.0.2.5 netmask 255.255.255.255"

    Remove the existing ifconfig_vtnet0 parameter and Replace the following values with those provided in your Vultr Customer Portal:

    • 192.0.0.4: Your Main IP address.
    • 192.0.2.5: Your newly assigned IPv4 address.
    • 192.0.0.6: Your DNS server.
    • 192.0.0.1: Your gateway IP.

    In the above configuration:

    • ifconfig_vtnet0: Sets your primary IP.
    • defaultrouter: Defines the system’s default gateway.
    • ifconfig_vtnet0_alias0: Adds an alias for the additional public IP using a /32 netmask.
    Note

    If your system uses a different network interface (such as xn0em0, or re0), replace vtnet0 accordingly. Use ifconfig to identify your active interface.

  11. Reboot the instance from the Vultr Customer Portal to apply the changes.
Configure multiple public IPv4 addresses on  Windows

Follow these steps to assign and configure multiple public IPv4 addresses on your Windows instance.

Configure the Main IP addresses

  1. Open the Windows Control Panel. You can access it from the Start menu.
  2. Click Network and Internet, then click Network and Sharing Center.
  3. Click Change adapter settings.
  4. Right-click the primary Ethernet adapter, then click Properties. The Ethernet Properties window will open.
  5. Select Internet Protocol Version 4 (TCP/IPv4), then click the Properties button. The Internet Protocol Version 4 (TCP/IPv4) Properties window will open.
  6. Check the option Use the following IP address: and populate the fields:
    • IP address: 192.0.0.4
    • Subnet mask: 255.255.254.0
    • Default gateway: 192.0.2.1

    Replace the above IP addresses with your Main IP address and correspondence details listed in the Vultr Customer Portal.

  7. Check the option Use the following DNS server addresses: and populate the fields:
    • Preferred DNS server: 192.0.0.6
    • Alternate DNS server: (leave blank)
  8. Click OK, then click OK again on the Ethernet Properties window. The main IPv4 has now been configured manually.
    Note

    It’s normal for the network connection to temporarily drop after saving the changes.

Add Additional IPv4 Addresses

After the primary IPv4 address is manually configured, follow these steps to add more public IP addresses.

  1. Repeat the steps above to open the Internet Protocol Version 4 (TCP/IPv4) Properties window for the same network adapter.
  2. Click the Advanced button.
  3. Under the IP addresses section, click Add to add another IP address.
  4. Enter your additional IP address:
    • IP address: 192.0.2.5
    • Subnet mask: 255.255.255.255
  5. Click OK on all open windows to apply the changes.
  6. Verify that the new IP address is assigned by running the below command in powershell.
    pwsh
    > ipconfig

    Output:

    Windows IP Configuration
    
    Ethernet adapter Ethernet Instance 0:
    
       Connection-specific DNS Suffix  . :
       Link-local IPv6 Address . . . . . : fe80::5400:5ff:fe8b:4d04%3
       IPv4 Address. . . . . . . . . . . : 192.0.2.5
       Subnet Mask . . . . . . . . . . . : 255.255.255.255
       IPv4 Address. . . . . . . . . . . : 192.0.0.4
       Subnet Mask . . . . . . . . . . . : 255.255.254.0
       Default Gateway . . . . . . . . . : 192.0.0.1

Conclusion

In this guide, you learned how to assign and configure multiple public IPv4 addresses to a Vultr Cloud Compute Instance across various operating systems, including UbuntuCentOSFreeBSD, and Windows. You added additional IP addresses through the Vultr Customer Portal and configured each system to recognize the new IPs using platform-specific tools like Netplanrc.conf, and the Windows Network Settings panel.

Leave a Reply

Your email address will not be published. Required fields are marked *