227541 - DNS: Network stalls when resolving domains

Status: RESOLVED DUPLICATE of bug 240759

(Core :: Networking, defect)

Description

[Brian Matzon]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007 Firebird/0.7
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007 Firebird/0.7

==
This is most likely a dupe, as I have experienced this bug quite often - but
doing a search for DNS did not find any duplicates
==
Sometimes when I just surf around, I sometimes experience that Mozilla
(Firebird) is doing a 'Resolving host xyz'. Whenever this occurs all other open
tabs are unable to connect to any sites - even previously visited.

When the domain has been resolved (existing or not) everything goes back to
normal, and pages load just fine again.

Reproducible: Sometimes

Steps to Reproduce:
I am not sure what is causing this - because when I type an invalid domain it
usually responds quite quickly that domain doesn't exist. Perhaps the DNS needs
to be slow?

Comment 1

[Darin Fisher]

brian: please try upgrading to a more recent build.  the DNS code in particular
has undergone a complete re-write since mozilla 1.5 (firebird 0.7).  please let
us know how the newer version behaves.  thanks!

Comment 2

[Lewis Rosenthal]

UserAgent: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.6a) Gecko/20031103
MultiZilla/1.5.0.4e

I've been seeing this since moving up from 1.4.1, but have attributed it to
something with my Squid proxy. However, now that you mention it, the behavior
I'm seeing is exactly as described here.

Lewis

Comment 3

[Lewis Rosenthal]

Hmmm... No sooner did I make that last post and try the link mentioned in Bug#
227549, when I had to kill Mozilla. This probably trashed my cache (I have a
very small browser cache, as I use Squid proxy). Upon restarting, the DNS
problem seems to be gone...

Lewis

Comment 4

[benc]

Lewis: if you have this problem when you connect to a site via proxy, that is
probably a separate bug, because, you browser does not do name resolution.

If you can isolate that in a post-DNS rewrite build, please file a new bug.

Brian: please upgrade and upate the bug.

Comment 5

[Brian Matzon]

I already upgraded and so far I haven't seen it. However it doesn't show itself
all the time. I'll close this bug if I haven't seen it by the end of the week.

Comment 6

[Brian Matzon]

It just happened again, using: 
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031203
Firebird/0.7+

I went to the site http://www.begroovy.com/ and the status bar said "resolving
begroovy.com", which ended in a :
"Address Not Found Error
www.begroovy.com could not be found. Please check the name and try again."

Meanwhile I quickly opened 3 more tabs, each going to domains I had visited
earlier today - and I got the same error on all three. Afterwards I visited one
of the failed tabs, and it loaded fine.

I have yet to be able to create a reproducible case, sorry

Comment 7

[benc]

I don't think we have many similar error reports, but the error message itself
is associated w/ two hard-to-reproduce problems:

bug 65924 and bug 164715.

Either your DNS server, or the domains DNS server is timing out. Since DNS
servers cache, this can be very intermittent.

Comment 8

[Andrew Hagen]

Confirming on 1.7 beta, Windows 98.

I see this all the time. It is a major aggravation. Nominating.

I am on a dial-up connection. I don't know if that has anything to do with it.

This problem seems to occur after a lot of browsing. When it occurs, Mozilla
just resolving new domain names for 30 seconds, a minute, or longer. Then it
starts working again.

This is a regression. I don't know when it started, but my guess is that it
started sometime in the 1.7 branch (after 1.6).

Comment 9

[Andrew Hagen]

Looking closer at the bug, the regression must have occurred between 1.4 and
1.5. The regression has worsened over time, I think.

Doing some Bugzilla querying, I came up with the following likely candidates for
the source of the regression.

bug 70213 (but that was UNIX-only)
bug 110565 (but that was IPv6)
bug 162871 (maybe)

My Bugzilla query is here: http://tinyurl.com/36tsf

Comment 10

[Andrew Hagen]

Removing nominations as the bug has been fixed. Dup'ing to that one.

Can't wait to try a new build.

*** This bug has been marked as a duplicate of 240759 ***

Comment 11

[Andrew Hagen]

Historical note: Bug 240759 comment 2 says this originated in Mozilla 1.1.

The new fix is working great.