GitHub user prashanthr2 added a comment to the discussion: Multi-subnet setup with VPN – System VMs unreachable and agent not connecting
@TheKunalSen No, adding .1.1 and .2.1 as internal DNS will not resolve this issue. The problem is not DNS, but how the networks are structured. In Apache CloudStack, Layer-2 (broadcast domain) consistency is expected per pod. When you place .2 network hosts in a pod under a .1-based zone without proper L2/L3 reachability, guest networking (DHCP, gateway, metadata, password injection) breaks which explains the VM boot/login issues you’re seeing. If you need to use hosts from multiple networks in the same zone, you must ensure proper network design (e.g., VLAN-backed guest networks or SDN) so that guest traffic is consistently reachable across those hosts. Otherwise, keep them in separate pods/zones where network boundaries are cleanly maintained. GitHub link: https://github.com/apache/cloudstack/discussions/12909#discussioncomment-16585523 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
