nscd cacher problem

JD jd1008 at gmail.com
Sat Jul 3 17:39:18 UTC 2010

  On 07/03/2010 12:53 AM, David Timms wrote:
> On 03/07/10 16:06, JD wrote:
>> Well, I have found that setting the interval to a longer time does
>> indeed help a lot!
>> However, the behavior of Firefox in resolving URL's  is still strange!
>> If I click on a link, firefox spends almost a full minute to resolve the
>> url,
>> so while it is waiting (spinning), I use the gnome terminal to
>> nslookup whatever-domain-it-was.com
> ...
> If you install wireshark, and then begin capture just before you make
> firefox go to a fresh site, ou should be able to see what is happening
> on the network.
> ps. for me its: ff tries ipv6, waits a minute for nonexistent response,
> request ipv4, and instantly has the answer and the page.
> wireshark makes it easy.
about::config shows that ipv6 is set to false,
so that cannot be the cause. But I will try wireshark.



More information about the users mailing list