On a Vista x64 PC with a wired connection to a Server 2003 Domain environment, a DHCP-assigned IP, and an empty hosts file, intermittently any attempt to ping, telnet or otherwise resolve a particular machine name (or FQDN) (and not always the same machine) will begin to fail with an "unable to resolve" error. The trigger that causes a machine name to stop resolving has not been identified.
However, when this situation occurs, nslookup is still able to successfully resolve the name, and access to the machine via IP address (ping, telnet, etc) is also successful.
UPDATE: "ipconfig /displaydns" returns:
myserver.mydomain.local
----------------------------------------
Name does not exist.
So it seems a lookup failure has been recorded. The lack of TTL normally present on all other entries returned is also concerning.
The simplest way I've found to recover this situation is to release and renew the DHCP lease; "ipconfig /flushdns" does not work.
How can I resolve this or how can I extract more diagnostic information to find the root cause?
Thank you