Vultr provides many flexible networking options for your cloud servers. In addition to the public network attached to every Vultr instance, you can configure up to five private networks per location. Private networks allow instances within a location to communicate without exposing the traffic to the public internet.
Note: Your network adapter names may not match the examples. See our article How to Find the Network Adapter Names for a Vultr Cloud Server.
Please see the guide How to Configure a Private Network at Vultr for general information about Vultr's private network feature.
Private networks do not have DHCP. When deploying a Vultr cloud server with private networking, you must manually configure the private adapters or supply your own DHCP server. We provide network configuration examples for many popular operating systems, pre-configured for your instance's IP addresses. You can find these by navigating to the settings screen
(1) for your server, then selecting IPv4
(2). Follow the networking configuration link
(3) to view the configuration examples.
The configurations in the customer portal are your best source of specific information. Please see below for step-by-step instructions with generic examples.
Use Ignition to configure the VPS for private networking. Before proceeding, make sure you understand how to use private networking at Vultr and create a private network at the deployment location. For more information, refer to our private networking documentation:
To configure a private network, include a YAML stanza in your FCC file that writes your network information. Replace the example IP address with your address.
storage: files: - path: /etc/NetworkManager/system-connections/ens7.nmconnection mode: 0600 overwrite: true contents: inline: | [connection] type=ethernet interface-name=ens7 [ipv4] method=manual addresses=10.10.10.10/20
The deployed VPS will have two adapters:
See a complete example in our Ignition documentation.
The Vultr API offers several endpoints to manage private networks.