Unable to resolve FQDN, hostname works
Posted
by
HannesFostie
on Server Fault
See other posts from Server Fault
or by HannesFostie
Published on 2011-05-18T08:46:22Z
Indexed on
2012/12/09
5:07 UTC
Read the original article
Hit count: 685
We are having an issue where computers who are not part of the domain cannot resolve the FQDN of a server (but regular hostname and ip do resolve). The strange thing is that this does work when the computer is added to the network.
Our domain name is rather long, its something along the lines of "team.dept.company.com", could that be it?
DHCP server passes along the proper DNS, Name and WINS servers, as well as the domain name. I thought that should've solved the problem, but apparently not really.
Our domain is still windows2003
EDIT: I am starting to believe I can narrow this down to a problem either with the vmware tools NIC drivers that are embedded in my winPE boot image, or to the fact that I'm trying to do this from inside a VM. Pinging a FQDN at the same time when using a different task sequence on a physical machine works.
© Server Fault or respective owner