On 05/16/2012 06:21 PM, Ed Greshko wrote:
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.
That value is already set to false.
Yes I did try Chrome.
Chrome resolves domain names as fast as nslookup .
After I browsed to a domain using Chrome, and it almost immediately
resolved and it brought in the page,
I quickly clicked on the FF workspace and browsed to same domain.
FF went into the looking up ...... spin dance.
Could it be that FF is not using same library as nslookup and Chrome?
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
