Long DNS lookup times with 9.2
All, I am using dhcp and when I use firefox to go to websites it takes for ever to do dns lookups. The browser just sort of sits then finally resolves the names. When I do a nslookup or a dig from the cli everything comes resolves very quickly. I have set it to static ip address and also static dns and the browser still takes for ever to resolv for some reason. I had a intel desktop 1000MT nic card I swapped that for a 3com nic and still the same issues. So I then installed a dns server locally on the box and change the resolv.conf to point to 127.0.0.1 there was no difference. Any ideas?
On Tue, 1 Mar 2005 08:29:15 -0500, Elijah Savage <esavage@digitalrage.org> wrote:
All,
I am using dhcp and when I use firefox to go to websites it takes for ever to do dns lookups. The browser just sort of sits then finally resolves the names. When I do a nslookup or a dig from the cli everything comes resolves very quickly. I have set it to static ip address and also static dns and the browser still takes for ever to resolv for some reason. I had a intel desktop 1000MT nic card I swapped that for a 3com nic and still the same issues. So I then installed a dns server locally on the box and change the resolv.conf to point to 127.0.0.1 there was no difference.
Any ideas?
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Hi, it has something to do with the UPv6 name resolving. There is an article in SuSE knowledge base how to disable IPv6, if you do not use it. It helped me and now I do not have these delays. Cheers Sunny -- Get Firefox http://www.spreadfirefox.com/?q=affiliates&id=10745&t=85
Sunny wrote:
On Tue, 1 Mar 2005 08:29:15 -0500, Elijah Savage <esavage@digitalrage.org> wrote:
All,
I am using dhcp and when I use firefox to go to websites it takes for ever to do dns lookups. The browser just sort of sits then finally resolves the names. When I do a nslookup or a dig from the cli everything comes resolves very quickly. I have set it to static ip address and also static dns and the browser still takes for ever to resolv for some reason. I had a intel desktop 1000MT nic card I swapped that for a 3com nic and still the same issues. So I then installed a dns server locally on the box and change the resolv.conf to point to 127.0.0.1 there was no difference.
Any ideas?
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Hi, it has something to do with the UPv6 name resolving. There is an article in SuSE knowledge base how to disable IPv6, if you do not use it. It helped me and now I do not have these delays.
Cheers Sunny
I think ipv6 is disabled by default in 9.2, isn't it? I know I had this problem with 9.1 (and had to edit /etc/modprobe.conf) but not in 9.2 Is /etc/resolv.conf being changed back dynamically? David -- Registered Linux User No 207521 The Linux Counter: http://counter.li.org/ "The above is my personal opinion and does not necessarily reflect that of the little voices in my head."
On Tue, 01 Mar 2005 18:44:37 +0300, David Robertson <derobertson@runbox.com> wrote:
Sunny wrote:
On Tue, 1 Mar 2005 08:29:15 -0500, Elijah Savage <esavage@digitalrage.org> wrote:
All,
I am using dhcp and when I use firefox to go to websites it takes for ever to do dns lookups. The browser just sort of sits then finally resolves the names. When I do a nslookup or a dig from the cli everything comes resolves very quickly. I have set it to static ip address and also static dns and the browser still takes for ever to resolv for some reason. I had a intel desktop 1000MT nic card I swapped that for a 3com nic and still the same issues. So I then installed a dns server locally on the box and change the resolv.conf to point to 127.0.0.1 there was no difference.
Any ideas?
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Hi, it has something to do with the UPv6 name resolving. There is an article in SuSE knowledge base how to disable IPv6, if you do not use it. It helped me and now I do not have these delays.
Cheers Sunny
I think ipv6 is disabled by default in 9.2, isn't it? I know I had this problem with 9.1 (and had to edit /etc/modprobe.conf) but not in 9.2 Is /etc/resolv.conf being changed back dynamically?
David
-- Registered Linux User No 207521 The Linux Counter: http://counter.li.org/
"The above is my personal opinion and does not necessarily reflect that of the little voices in my head."
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
I can't remember, but in that article 9.2 was mentioned as well. One way or another, the OP didn't say what version he uses. But as I see, he has solved the problem so far, so it doesn't matter. Cheers Sunny -- Get Firefox http://www.spreadfirefox.com/?q=affiliates&id=10745&t=85
On Tuesday 01 March 2005 08:29, Elijah Savage wrote: <snip>
Any ideas?
Hi Elijah, Here's what I'd do if I were "in the driver's seat": YaST -> Network Devices -> Network Cards under "Network cards configuration"... -> click 'Change' under 'Already configured devices' -> your nic should already be highlighted; click 'Edit' -> verify the Automatic address setup (via DHCP) checkbox is selected -> click 'Host name and name server setting' then 'Accept' (not 'Modify') -> verify and jot down the existing entries for Name Server 1 & 2 (3?) + Domain Search 1 & 2 (3?) I like to have these for later reference. -> verify the 'Update name servers and search list via DHCP checkbox is selected -> click 'Back' then 'Routing'; verify your default gateway is entered here. (the one in my router is 192.168.1.1) -> uncheck the 'Enable IP Forwarding' checkbox if it has been accidentally selected previously -> click 'Back' then 'Advanced' and 'DHCP Client Options' -> leave DHCP Client Identifier blank; verify 'Host Name to Send' is set to "AUTO" -> click 'Next' to have YaST complete this configuration -> in Firefox, select 'Edit' and 'Preferences' -> select 'General' in the left panel, then 'Connection Settings' on the right -> verify these settings are appropriate for your environment (select 'Direct connection...' unless you're using a proxy) -> you should see 'localhost, 127.0.0.1' in the 'No Proxy for:' field -> click 'OK' -> enter 'about:config' in the main address bar. -> scroll down until you see this entry: user_pref("network.dns.disableIPv6", false); -> right-click on it and toggle it to "true" -> close and restart Firefox. -> go for a test drive and I hope you have improved results In my opinion, all things being equal, Firefox /does/ seem a smidgen slower on this machine than I expected it to be. But it's performance isn't /bad/ either -- just possibly a little disappointing after all the hype? good luck & regards! - Carl -- _______________________________________________________________________ C. E. Hartung Business Development & Support Services http://www.cehartung.com/ carlh@cehartung.com Dover Foxcroft, Maine, USA Public Keys 68396713 & F8207216 Reg. Linux User #350527 http://counter.li.org/
On Tuesday 01 March 2005 10:35, Carl E. Hartung wrote: ...................<snip a bunch of stuff>..................
-> in Firefox, select 'Edit' and 'Preferences'
-> select 'General' in the left panel, then 'Connection Settings' on the right
-> verify these settings are appropriate for your environment (select 'Direct connection...' unless you're using a proxy)
-> you should see 'localhost, 127.0.0.1' in the 'No Proxy for:' field
-> click 'OK'
-> enter 'about:config' in the main address bar.
-> scroll down until you see this entry:
user_pref("network.dns.disableIPv6", false);
-> right-click on it and toggle it to "true"
-> close and restart Firefox.
-> go for a test drive and I hope you have improved results
In my opinion, all things being equal, Firefox /does/ seem a smidgen slower on this machine than I expected it to be. But it's performance isn't /bad/ either -- just possibly a little disappointing after all the hype?
Carl, And how about someone who is NOT running a network and has the same very slow loading problem with Firefox? Does ipv6 enter into also ? Bob S.
On Wednesday 02 March 2005 00:36, B. Stia wrote: <snip>
And how about someone who is NOT running a network and has the same very slow loading problem with Firefox? Does ipv6 enter into also ?
Hi Bob, The short answer is "I believe so." As you surmised, there were two issues being addressed by my recommended course of action to the OP (note: I did not call it a recommended course of action for every newbie who happens to stumble upon this thread): - part 'a' would have restored his system to SuSE's default (and his original) dhcp client configuration. I say "would have" because, in his reply, he wrote that he'd already accomplished that by the time he got my post. - part 'b' is the Firefox IPv6 'tweak', which wasn't invented or discovered by me, but purloined off the net. The tweak is maybe a one or two minute experiment, at most. Right click, modify, close browser and test drive. It worked for me, it has worked for others so I'm assuming it's worth checking out whether you're running a network or not. If it causes you problems or there is no discernable change, it is easy enough to set back. regards, - Carl -- _______________________________________________________________________ C. E. Hartung Business Development & Support Services http://www.cehartung.com/ carlh@cehartung.com Dover Foxcroft, Maine, USA Public Keys 68396713 & F8207216 Reg. Linux User #350527 http://counter.li.org/
Hi All, Why has no one responded to my post about the default .doubleclick.net entry in Firefox preferences? Does this mean it's OK to discuss browser speed 'tweaks' and sluggish dns resolution but it is not OK to discuss a possible security breach? I say "possible" because I haven't been able to figure out what the entry means or what it does. - Carl -- _______________________________________________________________________ C. E. Hartung Business Development & Support Services http://www.cehartung.com/ carlh@cehartung.com Dover Foxcroft, Maine, USA Public Keys 68396713 & F8207216 Reg. Linux User #350527 http://counter.li.org/
[Hmmm ... KMail appears not to let me trim references when replying...] On Wednesday 02 March 2005 12:57, Carl E. Hartung wrote:
Why has no one responded to my post about the default .doubleclick.net entry in Firefox preferences?
Er, because nobody here knows anything about it? You could try a FireFox list/group/board rather than a SuSE one ... ... or you could google for it. Top hit for search term 'ipv4onlydomains' suggests (in italian) that it's simply that the doubleclick.net domain has known problems with IPv6, and it's therefore helpfully forcing IPv4 for that domain to avoid .... (back on topic for this thread) DNS black hole / timeout problems when lookups are made and fetches attempted from that domain. Subsequent hits also have similar comments, and this bug (linked to from the 6th hit) seems to confirm them. https://bugzilla.mozilla.org/show_bug.cgi?id=68796#c83 -- Bill
On Wednesday 02 March 2005 08:17, William Gallafent wrote:
[Hmmm ... KMail appears not to let me trim references when replying...]
It works here :-)
Er, because nobody here knows anything about it? You could try a FireFox list/group/board rather than a SuSE one ...
I appreciate you paying attention and responding, but that was precisely my point. Subtle, but true: We (i.e. some of us on "the SLE list") had just engaged in a troubleshooting session and discussion about Firefox vis a vis slow dns resolutions (on a SuSE system) and the IPv6 preferences 'tweak.'. Subscribers were paying attention and got involved in that one, so I was just expressing surprise at not getting a single response to my post the same day. For the record, I /did/ point out that my version of Firefox had come from one of the established SuSE (distribution-specific, not official) apt repositories -- hence the tie-in to this list.
... or you could google for it.
I already explained that I googled and read extensively. A plethora of hits and seemingly endless discussions with no clear-cut explanations or answers. That's why I turned to the list.
I landed on many sites during my research on this, but you struck gold: You found *the* thread where the developers discussed and resolved this. Good job! I now have an authoritative answer! :-) Funnily enough, it turns out that the prefs entry with the ".doubleclick.net" value and the OP's success with the IPv6 'tweak' are actually related. They are both discussed in the the thread you found, Bill. For the curious: The prefs entry with the ".doubleclick.net" value is not only harmless, but needed in certain cases. It is an IPv6 _blacklist_ used in cases where a dns server is misbehaving. Read the entire thread at the link Bill provided for the complete technical explanation. Thanks Bill! regards, - Carl p.s.: And yes, the OP of this thread reported back that the IPv6 'tweak' worked, so his problem is solved, my question is answered and this thread deserves to be closed. -- _______________________________________________________________________ C. E. Hartung Business Development & Support Services http://www.cehartung.com/ carlh@cehartung.com Dover Foxcroft, Maine, USA Public Keys 68396713 & F8207216 Reg. Linux User #350527 http://counter.li.org/
From: "Elijah Savage" <esavage@digitalrage.org>
All,
I am using dhcp and when I use firefox to go to websites it takes for ever to do dns lookups. The browser just sort of sits then finally resolves the names. When I do a nslookup or a dig from the cli everything comes resolves very quickly. I have set it to static ip address and also static dns and the browser still takes for ever to resolv for some reason. I had a intel desktop 1000MT nic card I swapped that for a 3com nic and still the same issues. So I then installed a dns server locally on the box and change the resolv.conf to point to 127.0.0.1 there was no difference.
Any ideas?
Uh... For Starters - What does your /etc/dhcpcd.conf and /etc/resolve.conf look like? You say "set it to Static IP?" What does /etc/hosts look like.
participants (7)
-
B. Stia -
Carl E. Hartung -
david rankin -
David Robertson -
Elijah Savage -
Sunny -
William Gallafent