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

Posted by Mark Hurd on Super User See other posts from Super User or by Mark Hurd
Published on 2010-06-12T12:21:46Z Indexed on 2010/06/12 12:24 UTC
Read the original article Hit count: 228

Filed under:

dns

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...

Manually transferred from stackoverflow.com

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

Posted by Mark Hurd on Stack Overflow See other posts from Stack Overflow or by Mark Hurd
Published on 2010-06-12T07:44:06Z Indexed on 2010/06/12 7:52 UTC
Read the original article Hit count: 228

Filed under:

Windows

|

dns

Contrary to this 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...

Developer IT