From: "Jack Pivac" <email at delphinus dot co dot nz>
> Lee Sharp wrote:
>> Did you try the "net stop" above? I know it seems wrong, but did you
>> make sure? Another way is to try "nslookup" and see if changing DNS
>> within nslookup works. When you change DNS in the IP properties, it
>> flushes the DNS cache, and I think that is what's actually fixing it.
>> And if you have a occasional problem that breaks the cache on one windows
>> machine, it will also do it to others.
> Yeah I did try that, and also tried changing DNS within nslookup with
> 'server x.x.x.x'
And this did not fix (even temporarily) the problem? Then try pointing the
m0n0wall DNS manually at 188.8.131.52 and 184.108.40.206 and overriding the ones
provided by DHCP. This will insure that your m0n0wall is getting a good
> Do you know _why_ it breaks it on other computers as well? i'm curious....
This one is easy. The DNS cache in Windows is about as stable as my
ex-girlfriend. If a lookup fails, it falls over to the secondary. It will
never fall back to primary unless the secondary fails. If you get a
corrupted lookup, it will stay in the cache. If you get a failed lookup
back from your DNS server, it will STAY failed in the cache, unless there is
a flush or a timeout. In general, when my internet connection is poor, the
first thing I do is turn off the DNS cache. It just saves headaches.
NOTE: 220.127.116.11 and 18.104.22.168 are 2 big DNS clusters in the US. (UUnet and
GTE) A quick tracert will tell you if they are close to you. If not, try
and find authoritative DNS servers for major backbones close to you, and use