On Monday 14 Jun 2004 03:16, C Hamel wrote:

...

Hello,

I'm using 9.1 professional with KDE. My computer is linked to a high-speed cable modem via a router. The Firefox browser is very slow in resolving sites. When I click on a link, it usually takes 30 seconds to a minute for Firefox to resolve the site and start loading the page. (The page loading is normally very fast once the site address is resolved.) We have another computer running Win 2K, and Firefox on that computer resolves site addresses very fast (within a second or two).

I tried using Konqueror on the Linux box, thinking that the problem was related to Firefox. But Konqueror is just as slot at resolving sites. So I figured that this must be a network configuration problem.

I tried plugging my Linux computer directly into the cable modem (bypassing the router), but there was no improvement. I went into YaST and deleted the network card configuration and then re-added it. Still no change. I added the following lines to the Firefox script, but again there was no improvement.

MOZILLA_NO_ASYNC_DNS=True export MOZILLA_NO_ASYNC_DNS

Finally, the top command doesn't show any processes hogging the CPU. System specs: 2 Ghz processor, 1 GB of RAM.

Has anyone experienced this problem or have any ideas how to solve it? Thanks very much for your help.

Dom I had that problem, yes. I think it is probably critical where the lines are

On Sunday 13 June 2004 20:19, Dom Incollingo wrote: placed... mine seems to work really well w/the line at the top of the script. -- ...CH SuSE 9 Works Linux user# 313696 Linux box# 199365

from experiance (SP) too early in the morning ...:-).. Linux only checks the first three entries in resolv.conf and in order of appearance from the top down. -- Linux user No: 256242 Machine No: 139931 G6NJR Pete also MSA registered "Quinton 11" A Linux Only area Happy bug hunting M$ clan PGN

Hello there,

The Firefox browser is very slow in resolving sites. When I click on a link, it

...

usually takes 30 seconds to a minute for Firefox to resolve the site and start loading the page.

The Sunday 2004-06-06 at 12:23 -0700, Brett A. Taylor wrote:

...

So the problem ... the new SUSE box gets an IP and everything totally When I ping, use host or dig, names are resolved instantly. But when I try and actually connect to a remote host,

Here's a solution that I picked up off the list. ########### START ############## Subject: Re: [SLE] 9.1 -- slow dns resolving On Sunday 06 June 2004 6:39 pm, Carlos E. R. wrote: there's

...

a 5+ second delay on the resolution.

Just a guess: dissable ipv6 (don't ask me how).

Took me a while to figure out how to do this, but I *think* this is what solved the problem. I made the following changes to /etc/modprobe.conf: alias net-pf-10 ipv6 changed to: alias net-pf-10 off and I commented out alias sit0 ipv6 ########### END ############## I am using it and I think that it works... So you might give it a try Regards, James

On Monday 14 June 2004 09:49 pm, Ed Harrison wrote:

** Reply to message from James PEARSON on Mon, 14 Jun 2004 23:54:34 +0200

...

Just a guess: dissable ipv6 (don't ask me how).

Took me a while to figure out how to do this, but I *think* this is what solved the problem. I made the following changes to /etc/modprobe.conf:

alias net-pf-10 ipv6

changed to:

alias net-pf-10 off

and I commented out alias sit0 ipv6 ########### END ##############

I am using it and I think that it works... So you might give it a try

Regards, James

I did this also and it solved my slowness.

OK guys and gals. Please excuse my ignorance. Just read the man page !!! Phew, talk about gobbledygook ! WHAT does ipv6 do ?? Looks like it should be important. Shouldn't we not disable it? Bob S. Bob S.

James PEARSON wrote:

Took me a while to figure out how to do this, but I *think* this is what solved the problem. I made the following changes to /etc/modprobe.conf:

alias net-pf-10 ipv6

changed to:

alias net-pf-10 off

and I commented out alias sit0 ipv6 ########### END ##############

I am using it and I think that it works... So you might give it a try

Regards, James

Thanks James. I made the two changes you described to the /etc/modprobe.conf file after the browser had already gotten faster (as described in the previous note). I think that the change to /etc/modprobe.conf may have speeded things up a tad more, but it's too early to be sure. I'll leave the changes in place for a few weeks and see how things go. Thanks for your help. Dom

On Tuesday 15 June 2004 01:04, John Andersen wrote:

On Monday 14 June 2004 18:42, Dom Incollingo wrote:

...

Is it possible that Windows 2000 automatically caches DNS information to circumvent any problems (slowness) with the ISP's DNS servers?  Is it possible/advisable to cache DNS information on Linux?

Don't know about Cache. But if you suspect your ISP's dns server is being slow, just reverse the order of the primary and secondary entries in resolv.conf and see it that helps.

I've been watching this thread with great interest - I'm running a static IP and it's been *very* noticeable in Firefox that there appears to be a lot of redundant(and slow) "resolving foo.com" states, so I'm suspecting this issue is unrelated to slow DNS servers. I tried the MOZILLA_NO_ASYNC_DNS suggestion, and it appeared to help right away - but after 12 hours it seems to be back to it's old behaviour. This is a real puzzler...and I'm hoping the upcoming new release of Firefox might address it. I don't see to be having the same problems in other browsers, but FF is my browser of choice. On the surface, there appears to be some sort of problem with DNS resolves not being cached properly. I shouldn't be doing a google.ca search, then immediately change a search term and sit there watching "resolving www.google.ca" for 5 seconds... Cheers, J.C. -- John Coldrick www.axyzfx.com Axyz Animation Houdini/Renderman/Discreet 425 Adelaide St W 416-504-0425 Toronto, ON Canada jc@axyzfx.com M5V 1S4 ----------------------------------------------------------------------- Entropy isn't what it used to be.

On Tuesday 15 June 2004 15:29, John Andersen wrote:

try: (as root) rcnscd status

Perhaps your own name server cache deamon is not running...

Seems to be running. However, I caught this today: http://slashdot.org/article.pl?sid=04/06/15/1427213&mode=thread&tid=126&tid=95 seems to have been some major net-wide DNS issues recently and probably is some fallout. I'm going to wait a few more days before worrying about this to ensure we're not chasing tails... Cheers, J.C. -- John Coldrick www.axyzfx.com Axyz Animation Houdini/Renderman/Discreet 425 Adelaide St W 416-504-0425 Toronto, ON Canada jc@axyzfx.com M5V 1S4 ----------------------------------------------------------------------- Millions long for immortality who do not know what to do with themselves on a rainy Sunday afternoon. -- Susan Ertz