TABLE OF CONTENTS

A BinaryLane VPC provides private IPv4 networking between your servers. If you only have one server, or are unlikely to need private connectivity between two or more servers, you likely do not need a VPC.


VPCs are free. There is no cost to create a VPC or to connect servers to one. You pay only for the servers themselves.


Virtual Private Cloud (VPC) is a technology that allows you to create your own virtual network within BinaryLane, that isolates your cloud servers on their own private network.


Each VPC has its own private IP address range that you select during creation, such as 10.240.0.0/16. Because the virtual network is dedicated to your use, you may use whatever IP address range you like.


How networking behaves when a server is attached to a VPC

Attaching a server to a VPC does not remove an allocated public IP address or prevent public connectivity. The network path used inside the operating system depends on the selected VPC networking mode.


There are two common networking modes for servers attached to a VPC:

  • Default mode (NAT mode)
    The server has one interface carrying its private VPC address. If the server has a public IP, BinaryLane maps public traffic to and from this interface through the platform gateway.

  • Dedicated Interface (Split NIC)
    The server receives two virtual interfaces: one public interface carrying the public IP and one private interface for VPC traffic. The private interface may need to be configured manually inside the operating system.


In NAT mode, public and private traffic share the VPC interface and platform network path. In Dedicated Interface mode, the public and VPC paths use separate interfaces and can be configured independently.


A VPC is typically used for private communication between servers, including database connections, monitoring, log shipping, configuration management and internal service tiers. For detailed routing behaviour and configuration guidance, see VPC Routing Tables and Default Route Troubleshooting.


Your IP addresses in a VPC

  • Joining a VPC does not change your public IP. Moving an existing server into a VPC keeps its public IPv4 address.
  • Your VPC IP stays the same. The VPC IP address you choose for a server is kept through reboots, power off and on, resizes (plan changes), rebuilds (reinstalling the operating system) and backup restores.
  • Windows servers in a VPC need to keep their public IP address and outbound internet access to reach our KMS servers and keep their Windows licence valid. See BinaryLane mPanel service IPs.


IPv6 and VPC behaviour

BinaryLane VPC private networking is currently IPv4-only.

IPv6 addresses are not available on NAT-mode VPC networking.

If you enable Split NIC (Dedicated Interface), your server has:

  • a public NIC (internet-facing), and
  • a private VPC NIC (internal VPC traffic).

In this mode, IPv6 can be assigned on the public NIC.

However, IPv6 traffic between two servers in the same VPC will use the public path (public NIC ↔ upstream ↔ public NIC), not the VPC private fabric.

For private east-west traffic (database, Elasticsearch, monitoring, etc.), use VPC private IPv4 addresses.


This is by design, and there is no plan to change it. If you need IPv6 between servers inside a private network, forward or tunnel it yourself over the IPv4 private network from a server that holds a public IPv6 address. A routed IPv6 /56 is used from the public side of the server it is routed to.


The Cloud Firewall does not support IPv6 either. A server's public IPv6 address is not covered by it, so use the firewall inside the server to control IPv6 traffic. See Cloud Firewall.


A VPC information page with example use-cases is available here.


The VPC guides are available here.