Creating a Private Internal Network
Internal networks allow your VMs to communicate with each other privately — without being exposed to the internet. This is ideal for separating web servers from database servers or creating multi-tier application architectures.
Network Types on Cloud679
| Network Type | Description | Use Case |
|---|---|---|
| Public Network | Internet-routable public IP addresses. VMs are directly accessible from the internet. | Web servers, APIs, remote access |
| Internal Network | Private network visible only within your VDC. VMs communicate with each other but are not publicly accessible. | Databases, backend services, internal tools |
Creating an Internal Network
- Log into manage.cloud679.com
- Go to Virtual Data Centers → click on your VDC
- Click the Networks tab
- Click Create Network
- Select Internal Network
- Enter a Name (e.g. backend-network)
- Enter a Subnet (e.g. 10.10.10.0/24)
- Click Save
???? Tip: Internal networks are completely isolated to your VDC. Other tenants cannot see or access your private networks.
Adding an Internal Network to a VM
You can add an internal network interface to an existing VM without rebooting:
- Open your VM from the Virtual Machines list
- Click Edit Hardware
- Click Add Network Card
- Select your internal network from the dropdown
- Set Connect to ON
- Click Save
- Restart the VM — the new interface will appear in the OS after reboot
Common Subnet Recommendations
| Use Case | Suggested Subnet |
|---|---|
| Small internal network (up to 254 hosts) | 10.10.10.0/24 |
| Medium internal network (up to 510 hosts) | 10.10.0.0/23 |
| Database tier | 10.20.20.0/24 |
| Management network | 172.16.0.0/24 |
