This is a very weird problem -- I am able to find my VM normally, but there are times when I can't find my VM in my company network, which is Windows based.
Below is what the symptoms. I.e., ping
was unable to find my VM, while nslookup
shows it just fine, even if I'm not specifying the FQDN. Again,
- my company network is Windows based,
- my VM is Linux based, and
- I am able to
dig
&ping
my VM, if and only if I'm using the FQDN, while - normally the short name works fine as well.
- I am able to
Symptoms from Windows side:
D:\>ping myvm.mycompany.com
Ping request could not find host myvm.mycompany.com. Please check the name and try
again.
D:\>nslookup myvm
Server: dns1.mycompany.com
Address: 192.168.25.200
Name: myvm.mycompany.com
Address: 192.168.18.244
D:\>ping myvm.mycompany.com
Ping request could not find host myvm.mycompany.com. Please check the name and try
again.
D:\>nslookup myvm
Server: dns1.mycompany.com
Address: 192.168.25.200
Name: myvm.mycompany.com
Address: 192.168.18.244
hosts
file and create a static connection to the server address provided its not subject to change. You can also make sure when your unable to ping said address your using the correct DNS servers. During these periods of downtime were the dns servers ( dns1.mycompany.com ) also down? You were able to do a nslookup because Windows keeps a cache.dig
&ping
my VM in my VM using it.