M
Magnus_Hansson
Guest
I am trying to set up a lab Failover cluster on Hyper-V running on a Windows 10 host. The setup is 3 Windows server 2016 trial: 1 Domains controller and 2 member servers, to participate in the cluster. The DC also acts as DNS and iSCSI-target hosting 3 cluster disks.
The problem is, the IP-configuration of the servers seems to change randomly. With each restart I can get a 10.1... a 172.16 or a 192.169 network. Sometimes the servers are on different nets (For example the DC having 172.xxx and the two members on 192.168). This messes up up the DNS setttings and the member servers sometimes falls out of the domain.
How can I control the DHCP within Hyper-V, and make sure the DNS-settings is correct?
Continue reading...
The problem is, the IP-configuration of the servers seems to change randomly. With each restart I can get a 10.1... a 172.16 or a 192.169 network. Sometimes the servers are on different nets (For example the DC having 172.xxx and the two members on 192.168). This messes up up the DNS setttings and the member servers sometimes falls out of the domain.
How can I control the DHCP within Hyper-V, and make sure the DNS-settings is correct?
Continue reading...