I"m having an issue related to DNS (hostnames) and my Hyper-V 2012 host, and I hope you all can help. I have a local network and every machine can ping the other just fine using IP Address.
However, none of my 'client' machines can PING my Hyper-V host (running Hyper-V 2012 Core) by hostname. It almost always returns "host not found". When I use NSLookup {Hyper-V hostname},
it correctly returns back the correct result. It's strictly Ping that is not working.
I'm going to detail my exact setup to help better troubleshoot this:
Wireless Router:
Netgear WNDR3700 router (v4)
DHCP Enabled, DNSMasq Enabled
Has Static entry for Machine 4 (below)
Machine 1:
Win8 Pro Desktop
Connected to Domain
Attached to Router: Wired
Dynamic IP address
DNS: gets DNS from Machine 4
Machine 2:
Windows 8 Pro (Surface Pro)
Connected to Workgroup (not Domain as Machine 1 is)
Attached to Router: Wireless
Dynamic IP address
DNS: Dynamic (i.e., Router)
Machine 3:
Windows Server 2012 Hyper-V (Core)
Connected to Workgroup
Attached to Router: Wired
Dynamic IP address
DNS: Dynamic (i.e., Router)
I have Enabled 'Reachable by Ping' in the command-line GUI
Machine 4:
**Virtual Machine**: Windows Server Essentials 2012
This machine is a Domain Controller (Machine 1 is a member of this Domain)
This is a Guest VM of Machine 3 (i.e., Machine 3 is hosting this VM)
Static IP address
Attached to Router: Wired (via Host OS).. this VM has an "external" network adapter that I specified
so it can communicate with other physical machines on the local network
DNS: Set to itself (127.0.0.1)
The #1 issue I am having is that Machine 3 (the Hyper-V HOST) can PING ALL the other machines successfully,
but NONE of the other machines (Machine 1, 2, or 4) can PING Machine 3 (the Hyper-V HOST).
Sometimes, very rarely, all of a sudden, Machine 3 is successfully pingable by the other 3 machines (For
example, Ping keeps giving host not found, but all of a sudden it starts working), but usually after 15-20 minutes, it stops working again.
Since Machine 1 is connected via Domain to Machine 4, and since Machine 4 is a Domain Controller, Machine
1's DNS is pointing to Machine 4. Machine 1 has no problems pinging all other machines besides Machine 3.
Regarding Machine 2 (Surface Pro), for the most part it works good, however, sometimes it has trouble pinging
Machine 1. Though it's a minor quirk and I blame that mostly on the Wifi adapter in the Surface Pro to being junky.
What's really crazy is that the Guest OS (Machine 4) of the Hyper-V host can NOT Ping it's Host OS by
hostname.
I am completely baffled. This is definitely a DNS issue but since it is isolated to the Hyper-V 2012
host, I thought it may be something with Hyper-V.
I would greatly appreciate any help you all can provide. I was up until 4am last night trying resolve this, and I am all out of ideas.
Thanks in advance.