Re: Mozilla resolving host problem
On 12/2/06, David Shultz [EMAIL PROTECTED] wrote: Whenever I browse any website, mozilla says Resolving www.google.com and waits for about 15 seconds to resolve the host. I've disabled ipv6 but the problem is still there. Also I've checked the isp nameserver and they are fine. Does anyone has the same problem? First of all I apologize for late reply. I messed up my system so had to reinstall everything. Sorry about that. After reinstall everything is working fine now. Don't have that delay. If anything goes wrong, I'll post back later. Again thanks to all for helping me. --David
Re: Mozilla resolving host problem
On 12/02/2006 01:40 PM, David Shultz wrote: Whenever I browse any website, mozilla says Resolving www.google.com http://www.google.com and waits for about 15 seconds to resolve the host. I've disabled ipv6 but the problem is still there. Also I've checked the isp nameserver and they are fine. Does anyone has the same problem? --David David, The replies so far suggest this may not be a simple problem. Again, for me, the fact that I can quickly resolve url with the host command, or any other web application, suggests that it's a mozilla/firefox bug. A quick look @ bugzilla finds this bug among the many open dns related bugs: https://bugzilla.mozilla.org/show_bug.cgi?id=234320 Bugzilla Bug 234320 DNS lookups take a very long time for a DNS server on the same LAN Last modified: 2006-06-27 10:55:26 PST Good luck! Ralph -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Mozilla resolving host problem
On Sat, Dec 02, 2006 at 01:35:34PM -0500, David Shultz wrote: Whenever I browse any website, mozilla says Resolving www.google.com and waits for about 15 seconds to resolve the host. I've disabled ipv6 but the problem is still there. Also I've checked the isp nameserver and they are fine. Does anyone has the same problem? This seems like a problem I had. I could go to any site *except* www.google.com, and various other search engines. I thought there was some sort of conspiracy going on. :-) This was with lynx-ssl and wget, i.e wget http://www.google.com/search?q=hipcrime; If I tried lynx http://www.google.com; it would either just sit there then time out or as per usual go to http://www.google.co.nz but then sit there and time out. It also happened if I tried yahoo.com, altavista, askjeeves. I couldn't search the net! Other sites were fine. On the other machine running unstable, this problem didn't occur. I was stumped. I installed links, and eveything has been fine since. Since this is a reasonably old laptop in the middle of being upgraded to etch, I decided to wait and revisit it later. Although I think I prefer links. Thanks for bringing it up and hope you find a solution. -- Chris. == ... the official version cannot be abandoned because the implication of rejecting it is far too disturbing: that we are subject to a government conspiracy of `X-Files' proportions and insidiousness. Letter to the LA Times Magazine, September 18, 2005. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Mozilla resolving host problem
David Shultz wrote: On 12/2/06, Ralph Katz wrote: Yes, I have the same symptoms on sarge with firefox 1.5.0.8 (from mozilla tarball) and network.dns.disableIPv6 true. While firefox is resolving the address, I can bring up a terminal, $ host 'url' and get an ip address long before firefox gets it. The problem is very intermittent and usually not a problem. Restarting firefox seems to help. (Rarely, I plug the ip directly into firefox.) Thanks for your reply. Do you know what is causing this problem? Because in my case restarting firefox or mozilla doesn't fix it. --David Do you have the machine's LAN card in DHCP configuration or does it have a static address? Is the machine connected to a router or to a modem? I had noticed a similar problem at my parents home, running Ubuntu and Firefox, and IIRC giving the Ubuntu machine a fixed address seemed to have solved the problem. -HS -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Mozilla resolving host problem
H.S. wrote: Do you have the machine's LAN card in DHCP configuration or does it have a static address? Is the machine connected to a router or to a modem? I had noticed a similar problem at my parents home, running Ubuntu and Firefox, and IIRC giving the Ubuntu machine a fixed address seemed to have solved the problem. -HS In hindsight, it might have been the explicit nameservers that were mentioned in the static configuration that did the trick. Not sure though. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Mozilla resolving host problem
Whenever I browse any website, mozilla says Resolving www.google.com and waits for about 15 seconds to resolve the host. I've disabled ipv6 but the problem is still there. Also I've checked the isp nameserver and they are fine. Does anyone has the same problem? --David
Re: Mozilla resolving host problem
On 12/02/2006 01:40 PM, David Shultz wrote: Whenever I browse any website, mozilla says Resolving www.google.com http://www.google.com and waits for about 15 seconds to resolve the host. I've disabled ipv6 but the problem is still there. Also I've checked the isp nameserver and they are fine. Does anyone has the same problem? --David Yes, I have the same symptoms on sarge with firefox 1.5.0.8 (from mozilla tarball) and network.dns.disableIPv6 true. While firefox is resolving the address, I can bring up a terminal, $ host 'url' and get an ip address long before firefox gets it. The problem is very intermittent and usually not a problem. Restarting firefox seems to help. (Rarely, I plug the ip directly into firefox.) Regards, Ralph -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Mozilla resolving host problem
On 12/2/06, Ralph Katz wrote: Yes, I have the same symptoms on sarge with firefox 1.5.0.8 (from mozilla tarball) and network.dns.disableIPv6 true. While firefox is resolving the address, I can bring up a terminal, $ host 'url' and get an ip address long before firefox gets it. The problem is very intermittent and usually not a problem. Restarting firefox seems to help. (Rarely, I plug the ip directly into firefox.) Thanks for your reply. Do you know what is causing this problem? Because in my case restarting firefox or mozilla doesn't fix it. --David
Re: Mozilla resolving host problem
On Sat, Dec 02, 2006 at 01:35:34PM -0500, David Shultz wrote: Whenever I browse any website, mozilla says Resolving www.google.com and waits for about 15 seconds to resolve the host. I've disabled ipv6 but the problem is still there. Also I've checked the isp nameserver and they are fine. Does anyone has the same problem? I'm not sure what the problem is. Presumably, your startup page is set to www.google.com. I have mine set to my home directory. I'm on slow dialup. Every time any browser goes to a new page (even if its been there before) it has to resolve it. Very annoying. If this is the problem, you could install a caching name server that would give a faster response. Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Mozilla resolving host problem
On Sat, 2006-12-02 at 13:35 -0500, David Shultz wrote: Whenever I browse any website, mozilla says Resolving www.google.com and waits for about 15 seconds to resolve the host. I've disabled ipv6 but the problem is still there. Also I've checked the isp nameserver and they are fine. Does anyone has the same problem? --David By any chance, have you switched ISPs recently? You may still have the DNS addresses of the old ISP, so everytime it resolves an IP, it has to go to an outside nameserver, causing very long resolution time. Just an idea... -- Szia: Nyizsa. -- Cut Postage Costs! The Pitney Bowes mailstation. 90-day free trial $50 free postage. http://tagline.bidsystem.com/fc/BgLEQfI4hXCLNJBegNaSJfbytXNiAFpBDSX4/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Mozilla resolving host problem
David Shultz wrote: Whenever I browse any website, mozilla says Resolving www.google.com http://www.google.com and waits for about 15 seconds to resolve the host. I've disabled ipv6 but the problem is still there. Also I've checked the isp nameserver and they are fine. Does anyone has the same problem? --David This sounds like it could be a couple of things that I have run into. First, it could be an mDNS(multicast dns) problem. That gave me fits for a while. I cured it one by uninstalling avahi-daemon, as I don't have use any software that relies on this function(I did this just to stop an unnecessary daemon), and also editing my /etc/resolv.conf file so it didn't contain a line that used the word local. This word being in resolv.conf is/was a bug in Avahi-daemon, IIRC, that caused all DNS lookups to be run as mDNS lookups first, and then go to the nameserver picked up through dhcp, or in /etc/network/interfaces if you're using static ip addresses, when the mDNS queries finally time out. Second was the ipv6 lookups. I fixed that by blacklisting the ipv6 module and all those extraneous dns queries disappeared. The way I found the mDNS problem with extremely long url resolution times was to start an ethereal/wireshark packet capture, and then fire up my browser. That's when I found that all dns queries were going to 224.0.0.xxx (mDNS). I think the bug is now fixed as I just reinstalled a laptop a few days ago and I didn't have to make any changes in resolv.conf. DNS worked correctly from the very first, and that hadn't happened with any Etch installs I'd done in the last month or so. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Mozilla resolving host problem
On 12/2/06, Douglas Tutty [EMAIL PROTECTED] wrote: On Sat, Dec 02, 2006 at 01:35:34PM -0500, David Shultz wrote: Whenever I browse any website, mozilla says Resolving www.google.com and waits for about 15 seconds to resolve the host. I've disabled ipv6 but the problem is still there. Also I've checked the isp nameserver and they are fine. Does anyone has the same problem? If this is the problem, you could install a caching name server that would give a faster response. Doug. Thanks Doug. Caching nameserver has done the trick. I've setup bind9 to act as a caching nameserver. Now it is a lot faster. Thanks to forum members for their help. --David
Re: Mozilla resolving host problem
With great regret, the problem has shown its ugly face again. mozilla again shows: Resolving host www.google.com and a delay. I didn't have any problem until yesterday when it started. By any chance, have you switched ISPs recently? You may still have the DNS addresses of the old ISP, so everytime it resolves an IP, it has to go to an outside nameserver No I didn't change my isp. I cured it one by uninstalling avahi-daemon, as I don't have use any software that relies on this function(I did this just to stop an unnecessary daemon) I'm using Debian Sarge and after looking into Synaptic, have found that there is no Avahi-daemon on debian Sarge(stable). Is there anything else I should do? --David
Re: Mozilla resolving host problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David Shultz wrote: With great regret, the problem has shown its ugly face again. mozilla again shows: Resolving host www.google.com http://www.google.com and a delay. I didn't have any problem until yesterday when it started. By any chance, have you switched ISPs recently? You may still have the DNS addresses of the old ISP, so everytime it resolves an IP, it has to go to an outside nameserver No I didn't change my isp. I cured it one by uninstalling avahi-daemon, as I don't have use any software that relies on this function(I did this just to stop an unnecessary daemon) I'm using Debian Sarge and after looking into Synaptic, have found that there is no Avahi-daemon on debian Sarge(stable). Is there anything else I should do? Make sure your /etc/resolv.conf is still has it's reference to your cacheing nameserver. Did bind9 stop for some reason. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFclNxu4tRirKTPYwRAhY0AJ0YYLx17u7KXLsSZ5OW6+uAbar9FACePExE zXmOL4TrI9THCYAvev1MJA4= =FXhq -END PGP SIGNATURE- begin:vcard fn:W Paul Mills n:Mills;W Paul org:The Mills Chaos In The USA adr:;;;Topeka;Kansas;;USA email;internet:[EMAIL PROTECTED] title:Electronics Technician note:Hint: remove -NOT x-mozilla-html:FALSE url:http://Mills-USA.com version:2.1 end:vcard
Re: resolving host
On 09/30/04 23:21, Haines Brown wrote: Ralph Katz [EMAIL PROTECTED] writes: What do you get when you try to resolve the address directly? Ex: ~$ time host www.debian.org www.debian.org has address 194.109.137.218 real0m0.071s user0m0.050s sys 0m0.010s That ain't molasses :) This opens a whole new perspective for me. Not to derail the thread, but I get: $ time host www.debian.org www.debian.org A 194.109.137.218 real 0m0.027s user 0m0.000s sys 0m0.000s The man and info time did not make clear to me what real, user and sys refer to. Would you inlighten me? What is the A? Why zero time for the user and sys? Haines, Beats me, I'm the average Joe that sits in this Ferrari called debian GNU/Linux and says, wow! :) Looks to me like your computer is faster or less busy than mine. man time does answer your question, but I can't explain it further. Regards. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: resolving host
On Fri, Oct 01, 2004 at 08:05:03PM -0400, Ralph Katz wrote: On 09/30/04 23:21, Haines Brown wrote: $ time host www.debian.org www.debian.org A 194.109.137.218 real 0m0.027s user 0m0.000s sys 0m0.000s The man and info time did not make clear to me what real, user and sys refer to. Would you inlighten me? What is the A? Why zero time for the user and sys? Haines, Beats me, I'm the average Joe that sits in this Ferrari called debian GNU/Linux and says, wow! :) As far as I understand, and I could be wrong - real is the real world time taken for the command to run. user is how long the command spent processing user-space code. sys is how long the command spent processing kernel-space code. Cheers, Tom -- But Officer, I stopped for the last one, and it was green! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: resolving host
Subject: resolving host Date: Thu, 30 Sep 2004 19:14:42 -0500 From: Your Name [EMAIL PROTECTED] Newsgroups: linux.debian.user I wonder why browsing is so slow with Mozilla in Debian (well, Libranet). Using the ip addresses of websites it is blazing fast.. but using the www address it is slower than molasses in January. Not just Mozilla, but even Firefox and Galeon behave the same way. I do not have this problem in my FC2 box. Any ideas? (besides dumping Libranet/Debian, I mean).. --- Your Name :) It's certainly not true for the rest of us. :) What do you get when you try to resolve the address directly? Ex: ~$ time host www.debian.org www.debian.org has address 194.109.137.218 real0m0.071s user0m0.050s sys 0m0.010s That ain't molasses :) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: resolving host
On Thursday 30 September 2004 19:45, Ralph Katz wrote: Subject: resolving host Date: Thu, 30 Sep 2004 19:14:42 -0500 From: Your Name [EMAIL PROTECTED] Newsgroups: linux.debian.user I wonder why browsing is so slow with Mozilla in Debian (well, Libranet). Using the ip addresses of websites it is blazing fast.. but using the www address it is slower than molasses in January. Not just Mozilla, but even Firefox and Galeon behave the same way. I do not have this problem in my FC2 box. Any ideas? (besides dumping Libranet/Debian, I mean).. What dns servers are you using in your resolv.conf? the dig tool prints the time it took to resolve names - do some experimenting with it. dnstracer can also be helpful. are you running any dns caching utility, like nscd? are they configured properly? -- _ _ _ _ _ _ _ _ _ _ _ _ _ / \ / \ / \ / \ / \ / \ / \ / \ / \ / \ / \ / \ / \ ( t | i | m | @ | i | t | . | k | p | t | . | c | c ) \_/ \_/ \_/ \_/ \_/ \_/ \_/ \_/ \_/ \_/ \_/ \_/ \_/ GPG key fingerprint = 1DEE CD9B 4808 F608 FBBF DC21 2807 D7D3 09CA 85BF -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
