nscd and DNS cache

[Ed Greshko]

On 05/17/2012 03:52 AM, JD wrote:
> Well, after running dnsmasq with the configuration I just emailed,
> I see the following behavior of firefox vs. running nslookup on command line.
>
> FF, even after resolving google.com only a minute ago, is still spinning saying:
> lookup up www.google.com
> whereas , on the command line, I run nslookup www.google.com
> and almost instantly, I get
> Server:        127.0.0.1
> Address:    127.0.0.1#53
>
> Non-authoritative answer:
> Name:    google.com
> Address: 74.125.239.1
> Name:    google.com
> Address: 74.125.239.2
> Name:    google.com
> Address: 74.125.239.3
> Name:    google.com
> Address: 74.125.239.4
> Name:    google.com
> Address: 74.125.239.5
> Name:    google.com
> Address: 74.125.239.6
> Name:    google.com
> Address: 74.125.239.7
> Name:    google.com
> Address: 74.125.239.8
> Name:    google.com
> Address: 74.125.239.9
> Name:    google.com
> Address: 74.125.239.14
> Name:    google.com
> Address: 74.125.239.0
>
> and FF is still spinning waiting for the resolution.
>
> Does anyone see this discrepancy? 

No....

Have you tried a different browser?  Chrome, or konqueror for example?

One SWAG would be to set network.dns.disableIPv6 to true in about:config.

-- 
Never be afraid to laugh at yourself, after all, you could be missing out on the joke
of the century. -- Dame Edna Everage