Public vs private networking
Every server gets a public IP for reaching the internet. Servers in the same region can also join a private network, which carries traffic between them without touching the public internet — faster, and it doesn't count against bandwidth the same way.
Creating a private network
Open Networking in the control panel and create a private network in your region. Attach servers to it, then configure the private interface on each server:
network:
version: 2
ethernets:
eth1:
addresses:
- 10.0.0.10/24Planning your address space
Pick a range from RFC 1918 space that won't collide with anything you already use, such as your office VPN. A /24 per environment is a comfortable default.
- 10.0.0.0/8 — large deployments, plenty of room
- 172.16.0.0/12 — a common choice that rarely collides
- 192.168.0.0/16 — fine for small setups, but often used by home routers
Hybrid connectivity
To connect Syniac infrastructure with on-premises equipment or another cloud, see the Hybrid Cloud page or talk to the team about private interconnect options.