The issue may not be yours.
I am a unix lover, but have recently installed WinXP Pro sp 2 (with the latest windows updates) in order to play a particular game and generally play around. I had the same OS & OS version again running for 2-3 months last year, with the same setup/settings, but did not have this problem. Anyway: here's the details..
WinXP pc (as described above)
linux server - nameserver for internal net + internet, not having any problems
linux router - but we wont be needing this.
Connected through LAN (ethernet), internal ip addresses.
NS + winpc are on the same subnet, so they have a "direct" connection. Preferred nameserver : my linux NS, secondary my router, which serves as a dns proxy (having the my NS as its own primary ns).
Out of the blue, some appz cannot resolve some hostnames. This happens even to my local domain, served by the nameserver being only 1 switch and two ethernet cables away.
For example, i have an index of my MRTG graphs which auto-reloads every x minutes or so. I always have that tab open @ my firefox, and all of a sudden i get a pop up telling me it can't resolve mrtg.mydomain.foo, though it has been resolving that for hours, and nothing's changed.
I do not use a proxy, by the way. So it s not likely that my proxy is messed up. I do not run a firewall, and nothing is blocking my computer from looking up that hostname.
I check with IE, same problem. Cannot resolve.
And then, the strangest thing happens, i cmd -> nslookup it, and whoop, there it is, perfectly resolved.
I recheck with IE and firefox and anyting, and they still can't resolve the poor thing.
I try cmd -> ipconfig /flusdns, nothing changes
If i try cmd -> ipconfig /registerdns, the problem's gone. The same thing if i "Repair" my network connection (which i suppose does the same thing).
Then after some random (or not, but haven't be able to notice that) time, i get the same error.
Now, in order to trace the problem, i ran some tcpdump-ing on the domain name port on my nameserver. The results show that Windows dont even bother looking up the hostname when i get the error. I mean i kept that dump running, and tried refreshing my browser (after seeing the popup), and there was no request sent. But when i nslookup-ed it (through command line), the nameserver did get an actual query and did reply.
I tried some googling, and microsoft support search, but did not find anything about this problem. I still did try some of the advice i found as a reply to other dns client problems, that looked they could help...
Does anyone have any idea or any suggestion? Thank you very much in advance.
I tried regediting the ttl of the dns cache, and other parameters, just so windows will use that cache as little as possible, and im waiting. But as the problem doesn't happen at a given time, or because of something known to me, i can not be sure, or "force" it to happen, so im not sure that any of that regedit stuff did actually fix the prob.
Still open to suggestions, because i really cant figure this one out, and it really makes no sense, and i cant allow that to myself