Hi Hean, The network domain is determined by this order - domain of the network - network domain of the account - network domain of the domain - network domain of the zone - cs + accountid + cloud.local (guest domain suffix of the zone)
You can update the network with a new network domain. -Wei On Wed, 29 Mar 2023 at 08:51, Hean Seng <[email protected]> wrote: > Hi > > I create a Advance zone that have 2 Pod . > > Pod 1 - Hypervisors (kvm) are using share storage . So I have 3 physical > network , One for Management and Guest, Second one for VLAN network > (Public). and another one for Storage network on NFS . > > Pod 2 - Hypervisors (KVM) on Local storage, For this I only need 2 Physical > network. One for Management, Guest, and Storage( basically just for > Secondary Storage), and another network for VLAN (public Traffic) > > > However for the zone ,creating it seems not able to do so . If choose 3 > physical network, all Hypervisors will need to have 3 physical network . > > Is this some sort of limitation here ? Or any work around ? > > > Another issue is , reverse dns name for VR is always resolve to > r-484-vm.cs4cloud.internal > > r-484-vm is the name of the virtual router. > > > > Can I know where to change the name cs4cloud.internal to my preference name > ? > > > -- > Regards, > Hean Seng >
