Unit 3.1: VDC Topology and Segmentation
Introduction
Unit 1.2 introduced the rule that a LAN is private until it is connected to the internet, and drew the layered shape that follows from it. This unit turns that shape into a network you can provision: which LANs exist, which addresses each one uses, which addresses must be reserved, and which components can and cannot be filtered.
These decisions are cheap on a whiteboard and expensive later. A managed service placed on an address that DHCP also hands out, a production endpoint on a dynamic public address, or a data tier reachable from a public LAN are all topology mistakes, and a firewall rule does not repair them. The unit ends by building FinCorp's private LANs and reserving the public addresses for the edge services of Units 3.3 and 3.6.
1. Topology Is the First Security Control
1.1 How the Software-Defined Network Behaves
IONOS CLOUD does not expose any physical or virtual switches. Switching, routing and forwarding are integrated into the network stack, and traffic distribution is handled internally. Each virtual network is logically isolated, so data in one subnet stays segregated from other subnets.
Two consequences shape the design. First, virtual entities connect to each other or to the internet only through virtual network interface cards (NICs); a server joins a LAN through a NIC. Second, if you want to route traffic between your private networks through a VM, you must configure that VM to perform routing and update the relevant route tables yourself. Plan every inter-LAN path as a component you own: a routing VM, a load balancer or a gateway.
The network has fixed capacity parameters that every tier inherits:
| Parameter | Size | Performance |
|---|---|---|
| Throughput, internal | MTU 1,500 | Up to 6 Gbps |
| Throughput, external | MTU 1,500 | Up to 6 Gbps |
As shown above, the MTU is 1,500 inside and outside the VDC. Keep every network interface in the guest operating system at 1,500; a larger value is a misconfiguration to roll back, not a tuning option.
1.2 The Three-Tier Layout
The layout follows from the LAN rule. A public edge LAN carries only the components that must accept connections from the internet: the listener of the Managed Application Load Balancer (ALB) in FinCorp's design. A private application LAN carries the stateless compute tier. A private data LAN carries the data services and has no internet access element at all.
Membership defines exposure. When you connect the internet access element to a LAN, it becomes public, and its private IP addresses become public addresses. Merging LANs has the same effect: a private LAN that is integrated into a public LAN also becomes a public LAN. Treat "connect to internet" and "merge LAN" as security changes that need the same review as a firewall change.
Outbound access from the private tiers does not require a public LAN. The Managed NAT Gateway connects only to private LANs and gives VMs internet access without exposing them through a public interface (Unit 3.6).
1.3 Why Filtering Cannot Replace Topology
Network Security Groups (NSGs) and the NIC-based firewall filter traffic of VMs and NICs. User-created VMs and their NICs can be members of an NSG; nodes of Managed Kubernetes node pools and suspended Cubes cannot be added. The managed load balancers bring their own filtering instead: the Managed Network Load Balancer (NLB), for example, comes with basic firewall rules that are applied automatically based on its forwarding rules and cannot be changed; additional firewall rules belong on the NICs of the targets.
The managed data services follow the same pattern: they attach to a LAN through an address you give them, and you filter the VMs that talk to them. A data tier that must never be reachable from the internet is therefore secured first by having no path to it: a private LAN with no internet access element, reached only from the application LAN through a deliberate component such as a private NLB (Unit 3.4). Unit 3.2 adds the filters on top.
2. Addressing the LANs
2.1 The Private IPv4 Plan
Any private IPv4 range pursuant to RFC 1918 can be used in private networks:
| Network address range | CIDR notation |
|---|---|
| 10.0.0.0 to 10.255.255.255 | 10.0.0.0/8 |
| 172.16.0.0 to 172.31.255.255 | 172.16.0.0/12 |
| 192.168.0.0 to 192.168.255.255 | 192.168.0.0/16 |
A new private LAN receives an automatically allocated private IPv4 block; when you do not set one, the default block size is /23. The DHCP service then assigns a private address to each NIC, and that address is assigned statically to the NIC's MAC address. You can enable or disable DHCP per NIC, and you can run your own DHCP server, for example for PXE boot, by clearing the DHCP check box on the NICs it serves.
Several ranges inside every LAN are reserved, and your address plan must respect them:
| Address range in the LAN | Used for | Design rule |
|---|---|---|
| .1 | The platform's DHCP server | Never assign it |
| .2 to .9 | Connecting managed services, such as VPN gateways or DBaaS resources | Give every managed service LAN connection an address from this range |
| .224 to .255 | Never handed out by automatic assignment (nor are .0 to .9) | Use for manual static server addresses that must not collide with DHCP |
| .225 | Default backend address of the ALB and the NLB toward their targets | Keep it free on any LAN where a load balancer backend will sit |
Automatic assignment also never hands out the first host address or the broadcast address of the block. The rule of thumb for each tier follows from this table. Let DHCP address the VMs, put every managed service on an address between .2 and .9, and keep any manual static server address in .224 to .255, away from .225 and the broadcast address. The VPN Gateway makes the reason concrete: its interface IP is not DHCP aware, so an address inside the DHCP range can collide with a VM.
2.2 Reserved Public IPv4
A NIC connected to the internet receives a public IPv4 address from DHCP. That address can change when you deallocate the VM with Power Stop or remove the network interface. Any endpoint that clients, partners or DNS records depend on therefore needs a reserved address.
Reserved IPv4 addresses cost 5.0 EUR per 30 days per address. Only contract owners, administrators and users with the Reserve IP Blocks privilege can reserve them. IONOS CLOUD reserves random addresses; you cannot reserve a specific IPv4 address. Each address can be used only once, but different addresses from one block can be used in different networks of the same region. Unit 2.1 covered the stickiness: addresses are region-bound, returned only as a block, and a returned address cannot be reserved again.
Reserved addresses are a prerequisite, not an option, for several edge services. A public ALB or NLB listener needs one, the Managed NAT Gateway and the VPN Gateway each require one, and IP failover groups work only with reserved public addresses (Unit 3.5). Count them at design time and reserve them in the VDC's region before you build.
2.3 IPv6 per LAN
IPv6 follows a different allocation model. Every VDC receives a public /56 IPv6 block. IPv6 is deactivated on every new LAN; when you activate it, the LAN receives a /64 from the VDC's /56, either one you select or one assigned automatically. Each connected NIC then receives a /80 block and a single /128 address, and up to 50 IPv6 addresses can be assigned per NIC without any reservation. IPv6 addresses are static and remain assigned when the VM restarts. Up to 256 IPv6-enabled LANs can exist per VDC.
Two facts constrain where IPv6 goes. The addresses are public IPv6 addresses on private and public LANs alike. And several managed services are IPv4 only: the ALB, the NLB, the NAT Gateway, IP failover and Managed Kubernetes. FinCorp therefore runs its edge and data path on IPv4 and leaves IPv6 deactivated on the data LAN.
2.4 FinCorp's Address Plan
FinCorp's production VDC fc-prod-fra-core (Unit 2.1) gets three LANs:
| LAN | Exposure | Members | Addressing |
|---|---|---|---|
fc-edge |
Public | ALB listener (Unit 3.3) | Reserved public IPv4 only |
fc-app |
Private | Portal servers in Zone 1 and Zone 2, ALB backend, NAT Gateway, NLB listener and VPN Gateway connections | DHCP for servers; ALB backend on .225; NAT Gateway, NLB listener and VPN Gateway on .2 to .9 |
fc-data |
Private, no internet access element | Data-tier servers, DBaaS connections, NLB backend | DHCP for servers; DBaaS on .2 to .9; NLB backend on .225 |
The team reserves one block of three addresses in de/fra for the ALB listener, the NAT Gateway and the VPN Gateway, at 15.0 EUR per 30 days in total. Each managed service address on fc-app is written into the plan now, so that nothing else takes it.
DCD Implementation Walkthrough
You will reserve FinCorp's edge addresses and build the two private LANs of fc-prod-fra-core with their first NICs. The public edge LAN gets its only member, the ALB's northern interface, in Unit 3.3. Server sizing is a placeholder here; Unit 4.1 sets the compute class.
Prerequisites: the VDC fc-prod-fra-core from Unit 2.1, created with the default network security group, and an account with the Reserve IP Blocks privilege or the Administrator role.
Build goal: Build the three-LAN topology with NICs and a reserved public IP.
Steps (in the Data Center Designer):
- Go to Menu > Network Services > IP Management and select + Reserve IP Blocks. Enter Name
fc-prod-fra-edge, Number of IPs3, and the Region of the VDC (Frankfurt). Confirm with Reserve IP Blocks. The block and its addresses appear on the right. - Go to Menu > Virtual Data Centers and open
fc-prod-fra-core. - Drag a Dedicated Core server element from the Palette into the Workspace. In the Settings tab, name it
fc-app-01and select Zone 1 as the Availability Zone. - Double-click the + icon on the server. This creates a NIC connected to a new private LAN. In the LAN tab of the Inspector pane, name the LAN
fc-app. - Add a second server
fc-app-02in Zone 2. Create its NIC and, in the Network tab, selectfc-appin the LAN drop-down list so that both servers share the application LAN. - Repeat steps 3 to 5 for the data tier: servers
fc-data-01(Zone 1) andfc-data-02(Zone 2) on a new private LAN namedfc-data. Do not connect the Internet element to either LAN. - For each NIC, open the Network tab and check the addressing: leave Primary IP automatic with DHCP selected for these servers. If a server needs a fixed private address, enter it manually, and take it from .224 to .255 (not .225).
- Leave the filtering for Unit 3.2. Every newly created VM in the VDC joins the default network security group automatically; the Network Security Groups field in the server's Settings tab is where Unit 3.2 assigns tier groups.
- Select PROVISION CHANGES, review the Validation tab of the Provision Data Center window, confirm with your password and select Provision Now.
- After provisioning, select each LAN in the Workspace and open the Members tab in the Inspector pane to read the allotted address range. Record it in the address plan before any managed service joins the LAN.
Common mistakes:
- Giving a managed service an address from the DHCP range. Use .2 to .9, and record each one in the plan.
- Using the DHCP public address of a VM as an endpoint. It can change on Power Stop or NIC removal; reserve the address instead.
- Dragging the Internet element onto a private tier "for patching". That converts the LAN and all its addresses to public; use the NAT Gateway (Unit 3.6).
- Assigning .225 to a server on a LAN that will hold a load balancer backend.
- Activating IPv6 on the data LAN without a requirement. The addresses are public, and the load balancers and NAT Gateway in front of it are IPv4 only.
- Reserving the edge block in a region other than the VDC's. The addresses cannot be used there.
Summary
Segmentation on IONOS CLOUD starts with LAN membership. There are no switches to configure and no implicit router between LANs, so a private LAN with no internet access element is the strongest isolation you can give a tier. Plan addresses around the platform's reserved ranges, put managed services on .2 to .9, reserve public IPv4 for every endpoint others depend on, and add IPv6 per LAN only where every component on the path supports it.
Key Points:
- No switches are exposed; routing between private LANs through a VM is your configuration, including route tables.
- A LAN connected to the internet, or merged into a public LAN, becomes public together with its addresses.
- Reserve .1 for DHCP, .2 to .9 for managed services, and keep .225 free where a load balancer backend will sit.
- Reserved IPv4 addresses cost 5.0 EUR per 30 days each, are random and region-bound, and are required by public listeners, the NAT Gateway, the VPN Gateway and IP failover.
- NSGs and the NIC firewall cover VMs and NICs only; the data tier is isolated first by topology.
Important Terminology:
- Public edge LAN: the only LAN connected to the internet access element, holding the public listeners and nothing else.
- Managed service range: the addresses .2 to .9 of each LAN, reserved for connecting managed services without DHCP collisions.