Servers get their public addresses from IP blocks you add in Infrastructure › IP pools. How an address reaches the server depends on the block: routed through the node (the default, which works with almost every hosting provider), bridged onto the node's uplink with a virtual MAC, bridged onto a VLAN, or shared behind NAT with port forwards. Which modes suit your provider is explained in Network modes.
On top of the addresses, servers can join private networks, customers can keep floating IPs and run load balancers, the panel can manage forward and reverse DNS, and each server has its own firewall on the node.
- IP pools: blocks, ranges and CSV import
- Routed IPv4 and IPv6
- NAT servers and port forwards, and websites by domain (beta)
- Bridged networking and VLANs (beta)
- Private networks
- Floating IPs and load balancers
- Hostnames, DNS and reverse DNS
- Duplicate address detection
- Server firewall and firewall templates
- IP poolsAdd IPv4, IPv6 and NAT blocks to a node, reserve addresses, set fixed MACs, and export or import a block's addresses as CSV.
- Routed IPv4 and IPv6How routed networking works, on-link and provider-routed IPv4 blocks (OVHcloud, Hetzner), IPv6 prefixes and IPv6-only servers.
- NAT servers and port forwardsSell servers behind NAT that share the node's public IPv4 address, and let customers forward ports of that address to their servers.
- Websites on NAT servers by domain BetaLet servers behind NAT host websites on the node's shared ports 80 and 443, routed by domain name, with the server keeping its own certificate.
- Bridged networkingPut servers on the node's uplink with their own MAC: the uplink bridge, OVHcloud virtual MACs made by the panel, Hetzner MACs and DHCP.
- VLANs BetaCarry tagged VLANs on a node's uplink, put on-link IPv4 blocks on them, and bridge servers onto the VLAN without touching the node's own network.
- Private networksJoin servers on a private network of their own, across every node, with traffic between nodes encrypted in a WireGuard mesh that the agents set up.
- Floating IPs and load balancersGive customers public addresses they move between their servers in seconds, and load balancers run by the node's agent with health checks.
- Hostnames, DNS and reverse DNSGenerated server names, the panel's domain, A and AAAA records through Cloudflare, and reverse DNS through provider APIs or by hand.
- Duplicate address detectionHow VMStack checks that an IP address is not used by another machine on the node's network before giving it out, and how to handle marks.
- Server firewall and firewall templatesThe per-server firewall enforced on the node, its rules, rate limits, country rules, hit counters and dropped-packet log, and firewall templates.