I have a Hyper-V virtual machine configured with its own DNS manager and entries for testing. The VM DNS manager is setup to forward all other requests to the "regular" DNS servers.
This all used to work fine, but now I am running into issues (possibly corresponds to about the time I changed the virtual machine's network adapter to bind to multiple static ip addresses - previously it was a single DHCP address).
The interesting thing is that I ping the VM DNS entries just fine. However, for the forwarded entries, nslookup succeeds, but ping fails, and no external internet sites can be accessed.
For example, here are the results for www.google.com, after a fresh
C:\Windows\system32>nslookup www.google.com Server: localhost Address: 127.0.0.1 Non-authoritative answer: Name: www.google.com Addresses: 2607:f8b0:4003:c01::68 126.96.36.199 188.8.131.52 184.108.40.206 220.127.116.11 18.104.22.168 22.214.171.124 C:\Windows\system32>ping www.google.com Ping request could not find host www.google.com. Please check the name and try again. C:\Windows\system32>ping 126.96.36.199 Pinging 188.8.131.52 with 32 bytes of data: PING: transmit failed. General failure. PING: transmit failed. General failure. PING: transmit failed. General failure. PING: transmit failed. General failure. Ping statistics for 184.108.40.206: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
But pinging my internally defined dns entries (defined in forward lookup zones) works fine.
With the static ip setup (multiple static ips on the same network connection, dns server set to 127.0.0.1 with forwarding to "official" dns servers), I can ping both dns entries defined on my VM and dns entries local to the wider internal network. However, I can't ping addresses on the Internet.
If I allow Windows to "diagnose" my network connection in the virtual machine, it suggests changing my VM adapter back to DHCP - if I allow it to do so, I can ping external internet (but not my VM dns entries). As soon as I switch it back to the static ip addresses, the problematic behavior exhibits itself again.
All assigned ip addresses are on the same subnet.
Here is a
C:\Windows\system32>tracert 220.127.116.11 Tracing route to oa-in-f106.1e100.net [18.104.22.168] over a maximum of 30 hops: 1 Transmit error: code 1231. Trace complete.
Why is my virtual server able to successfully resolve external DNS entries, but not actually connect to them?