This problem concerns an internal DNS server that for some reason sometimes fails to resolve the host names of some machines on the network. When it fails to resolve a host name, and this can happen on any client machine, the following commands return the following:
ipconfig /displaydns:
vm1host.domain.local - Name does not exist.
nslookup vm1host:
dnsserver1.domain.local can't find vm1host: Non-existent domain
ping vm1host:
Ping request could not find host vm1host. Please check the name and try again.
tracert vm1host:
Unable to resolve target system name vm1host.
nslookup vm1host.domain.local :
dnsserver1.domain.local can't find vm1host.domain.local: Non-existent domain
ping vm1host.domain.local:
Ping request could not find host vm1host.domain.local Please check the name and try again.
tracert vm1host.domain.local:
Unable to resolve target system name vm1host.domain.local.
nslookup <vm1-ip-address>
:
Works Ok...
ping <vm1-ip-address>
:
Works Ok...
tracert <vm1-ip-address>
:
Works Ok... (also displays vm1host.domain.local)
Interestingly, tracert resolves the name appropriately using only 2 hops.
Even if subsequently nslookup/ping the host name, I get the same error messages above.
Flushing the dns does nothing, and even if it did it would not solve the underlying problem since it is experienced by all client machines.
What does the failure of nslookup/ping but the success of tracert suggest about the underlying problem?
local.
?