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.
A few important points about private networks:
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.
You can see generic examples of those configurations here:
You can create up to 5 private networks per location. Private networks can not communicate between locations, regardless of IP addressing. For example, server instances in Miami can not see private networks in Dallas. To get started:
Choose Add Network.
Select a location.
Accept the suggested IP network address range, or supply your own.
You can use any RFC1918 private address range, 10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16. When you attach Vultr products such as Load Balancers to the private network, they will automatically choose non-conflicting addresses in the range you declare here.
Click Add Network.
After you've created a private network, you can assign it to an instance. Use addresses in the same range you chose in step 7 to be compatible with other Vultr products.
You can also segment groups of instances by using multiple private networks.
Shown below is a portion of the IPv4 Settings screen for an example instance.
(1)link to create one.
(3)and click Attach Network
The server will reboot to activate the network adapter.
The Vultr API offers several endpoints to manage private networks.
If you'd like to see examples demonstrating multiple public as well as private networks at Vultr, see these guides: