When I start my Windows 10 Pro host, resolving the guest's name works as expected. I get the address for the guest that is in the guest's settings and is in both the /etc/hosts file in the guest and in the c:\windows\system32\drivers\etc\hosts on the host.
However, during the guest boot process, the address of the guest seen by the host, but not on the guest changes to 2.168.179.110. Always the same IP.
Here is a ping before starting the VM (naturally it fails, but note the address resolution). Hyper-V manager is already open at this point:
>ping -n 1 tableau-vm.mshome.net
Pinging tableau-vm.mshome.net [192.168.3.2] with 32 bytes of data:
Request timed out.During boot of the guest, the output from the same command on the host changes to
>ping -n 1 tableau-vm.mshome.net
Pinging tableau-vm.mshome.net [2.168.179.110] with 32 bytes of data:
Request timed out.
Ping statistics for 2.168.179.110: Packets: Sent = 1, Received = 0, Lost = 1 (100% loss),If I don't use the FQDN then I get the correct IP (and the FQDN is shown):
>ping -n 1 tableau-vm
Pinging tableau-vm.mshome.net [192.168.3.2] with 32 bytes of data:
Reply from 192.168.3.2: bytes=32 time<1ms TTL=64
Ping statistics for 192.168.3.2: Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0msSomething is overriding the resolution in c:\windows\system32\drivers\etc\hosts, I just don't know what. I cannot find any reference to this IP anywhere in the guest's /etc.
For the record:
- I have the default switch and an Internal Network switch in the Hyper-V switch manager.
- The guest's NIC is connect to said Internal Network switch.
TIA!
1 Reset to default