273112 - DNS stop resolving all pages in SUSE Linux 9.1 Personal

Status: RESOLVED EXPIRED

(Core :: Networking, defect)

Description

[Djoni]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040913

After a few minutes browsing the internet, Mozilla 1.7.3 craches the DNSr from
my router ADSL. But just Mozilla 1.7.3 in SUSE Linux 9.1 Personal. I had install
Firefox 1.0 in a clean install of SUSE and I didn't have the same problem, and
after install mozilla crashes again.
* I have tried in other computer and I saw the same think.

Reproducible: Always
Steps to Reproduce:
1.Install SUSE 9.1 Personal and navigate with Konqueror. Works Fine.
2.Install Mozilla 1.7.3, after a few minutes everything stop work.
3.

Actual Results:  
Crashes DNSr in ADSL Router.

Comment 1

[Yves Lambert]

Well I met the same problem with mandrake distribution (1.72)some one told me he
had the same problem with suse/mozilla 1.75 too i send him a brief for him to
confirm here.

I've been using 1.7 nightlies and 1.7 prereleases and release and i did not
notice the problem. 
I am going to try and reproduce the problem with trunk nightlies and 1.7
nightlies too anyhow the problem seems to be specific to 1.71 and higher releases
see bug: 267023 too (maybe duplicate)

Comment 2

[Yves Lambert]

It is the same thing in mozilla trunk : I did not deeply test it but what
happens is that :
When mozilla first query for DNS it cache it and get theb expiration (TTL) when
DNS expires it is unable to query again anf hangs

Steps to reproduce : 
Version : trunk
1. wait for DNS cache to expire
2. try to open a pop3, imap an ftp or an http that have been already open

Actual result : DNS resolution hangs up
Expected result : DNS resolution activates

Reporter : Please 
1. set severity to major : this is not a blocker
2. test the problem with a nightly release
If you got the same problem please set version to "trunk"

Comment 3

[Yves Lambert]

(In reply to comment #2)
>  what
> happens is that :

I mean : what seems to happen

Comment 4

[Andrew Schultz]

does not block development

Comment 5

[Yves Lambert]

This occurs in trunk too. 
It seems that the DNS resolution works again after several minutes

Comment 6

[Yves Lambert]

162871 should be reopenned

Comment 7

[Darin Fisher]

by default, the result of DNS queries are "cached" for 60 seconds.  you can
alter this behavior by adjusting the value of the network.dnsCacheExpiration
pref (seconds).

Comment 8

[Yves Lambert]

This bug is actually a duplicatre of bug: 206107

(In reply to comment #1)

> see bug: 267023 too (maybe duplicate)

I meant 206107

Comment 9

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 10

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.