After a period of time, nslookup still works, but pinging, and an auto-refeshed website, fails

Question

Contrary to this SO question this is for a dotted name (gw.localnet.au), and it doesn't happen straight away. Only after some period of time (quite a long time, possibly days).

In fact this is for my ADSL router and its internal IP address which I have named within the router itself and in my Windows Server 2003 Domain Controller DNS Service. Specifically, localnet.au is a Active-Directory-backed primary domain.

In fact, an ipconfig /flushdns may fix the problem, but only after a while (about the time it took me to type in this question :-) ).

That doesn't explain the root cause though...

EDIT: My machine that is failing is Windows XP SP3.

Manually transferred from stackoverflow.com

Answer 1

I had (and still have) the same problem Can ping IP address and nslookup hostname but cannot ping hostname. It seems like every time I do ipconfig /flushdns it goes away but I sometimes do this several times a day without any other changes to my network connection or rebooting. I think the issue is Windows is deciding to use your secondary DNS server more than your primary DNS server for everything other than nslookup commands. Atleast for me, my primary DNS server forwards almost everything to my secondary anyway but my secondary doesn't know about the host I'm trying to ping. To answer your question, I never really found the root cause.