DNS Resolution and DHCP

[Guest]

I have about 120 Win XP Pro users on my network, all configured to use DHCP.
Most network fuctions are working well, but I have recently found a name
resolution problem after adding a new host to the network.

About 10% of the users cannot resolve the new host name. If I ping the
host, I get the message "ping request could not find host". But if I run
nslookup, I get the correct IP address immediately. The responses are the
same if I use the simple host name or the FQDN.

I have run ipconfig /flushdns countless times with no effect. (I have
noticed that even after running /flushdns some machines still have many
entries when I run /displaydns.)

I can make name resolution work by changing the IP configuration from
'obtain DNS server address automatically' to 'use the following DNS server
addresses' and specifying the SAME DNS servers as provided by DHCP. Name
resolution then works. If I change the settings back to automatic, name
resolution works for about 30 minutes and then stops.

From the number of posts on this issue, it seems to be a 'known' issue, but
I have not been able to find a good fix. Does anyone know what the root
cause is, and how to fix it?

Thanks,
Joe

 

[Guest]

Tom,
I have two Win2k3 domain controllers, both running DNS for the internal
domain. The domain controllers provide all core services such as DNS, DHCP,
WINS, and IAS. The DNS servers point to each other for secondary DNS.

Hope that helps.
Joe

 

[Guest]

Is your DNS server an internal server or a public server? Is the server
Windows 2003 Server? Need more info.

 

[Guest]

Might there be a competing DHCP server visible somewhere, giving-out wrong
settings?

 

[Guest]

Negative. I've confirmed the IP settings through ipconfig. The assigned DNS
servers are the same that I would set manually. It works if assigned
manually, but does not work if assigned via DHCP.
Joe

 

[Guest]

Anyone have any other thoughts on this?
Thanks,
Joe

 

[Chuck [MVP]]

:

Anyone have any other thoughts on this?
Thanks,
Joe

Try diagnosing the problem. Look at logs from "browstat status", "ipconfig
/all", "net config server", and "net config workstation", from the problem
computer, and from 2 properly working computers. Read this article, and linked
articles, and follow instructions precisely (download browstat!):
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>
http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp

Is this the last computer to be added, or do you plan to add any more? How are
you setting up the computers - do you have a manual script, a configuration
utility, a cloning process, what?

--
Cheers,
Chuck, MS-MVP 2005-2007 [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.