Here is a tracert result: C:\Windows\system32>tracert 173.194.64. As soon as I switch it back to the static ip addresses, the problematic behavior exhibits itself again.Īll assigned ip addresses are on the same subnet. 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). However, I can't ping addresses on the Internet. 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. Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),īut pinging my internally defined dns entries (defined in forward lookup zones) works fine. However, for the forwarded entries, nslookup succeeds, but ping fails, and no external internet sites can be accessed.įor example, here are the results for after a fresh ipconfig /flushdns: C:\Windows\system32>nslookup Server: localhostĬ:\Windows\system32>ping Ping request could not find host Please check the name and try again. The interesting thing is that I ping the VM DNS entries just fine. 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 VM DNS manager is setup to forward all other requests to the "regular" DNS servers. It is a common way that servers allow configurion 0.0.0.0 to express binding to all IPv4 the host has (see ). I have a Hyper-V virtual machine configured with its own DNS manager and entries for testing. 1 The IP 0.0.0.0 is not the IP address the server is binding/listening too.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |