A /27 range of IP Addresses inside my /24 Subnet in Azure vNet isn’t working

If I assign 10.1.2.95 to a VM… It works without issue, but if I try using .96 thru .127 (aka 10.1.2.96/27 CIDR) then I can no longer access the VM directly (only via a jump box on the same subnet as the VM) and the VM cannot reach anything outside the subnet (including DNS servers, or other VMs in peered vNets).

Has anyone seen this happen in Azure before? I checked all the NSG/UDR settings I could find, and already filled a support ticket, but this is driving me crazy!

submitted by /u/gbrayut
[link] [comments]

Leave a Reply