Closed Bug 164593 Opened 22 years ago Closed 16 years ago

DNS: stopping/reloading causes DNS failures?

Categories

(Core :: Networking, defect)

x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: ve2cii, Unassigned)

References

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1b) Gecko/20020722 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1b) Gecko/2002072204 I have had this problem with all versions of netscape and mozilla. I can duplicate this problem jusr about every time. The version of bind I am using is 9.1.0. I also had this problem with previous versions of bind. Here is the problem. When mozilla queries named and I stop mozilla during the query. It can then no longer find any url's. It seems to loose touch with the dns. I then restart mozilla and all is well again. Also it looses touch sometimes with the dns if it can not find a url. I tried doing a search of a url after mozilla shows the problem to make sure it was not bind. mozilla cannot find the url but the query of named does find the url, so I concluded it was not a bind problem. Reproducible: Always Steps to Reproduce: 1. Stop mozilla during it's query of the dns. 2. Do a reload of the page or go to another url 3. mozilla can no longer find any url's Actual Results: I now have to restart mozilla and all is well. Expected Results: It should not be getting stuck on dns queries. You can contact me for additional information, but I don't know what else I can say.
I's get a tcpdump of your net for port domain (dns) to se if there is further traffic from the browser to your nameserver. This will tell us where the process is "hung" - i.e. in the browser (it's not actually sending out any more name queries), or your named is not infact responding to mozilla queries (perhaps you can put named in debugging mode) Second to that, you can "gdb /somewhere/mozilla-bin process_id" and then do a "bt" to see if one of the mozilla process is hung up. I believe mozilla now uses one process as a asynchronous dns resolver.
I think I'm seeing the same thing: I don't run a local name server. If I attapt to browse to a page, while ADSL modem/router is off,(or if through dailup when PPP is disabled) then the page I browse to fails to load. All further pages fail to load regardless of wether connected to the internet or not. I also can restore browsing by closing & restarting Mozilla. I might expect failure while I'm offline, but I wouldn't expect failure when restore connection. Will try the tcpdump test soon.
I have just confirmed that my problem isn't this bug. Sorry.
May be related to bug 117613, and bug 151683.
I think this is related to something Darin wanted me to verify, but I can't find it...
Summary: dns problem → DNS: problem
Whiteboard: dupeme
*** Bug 164988 has been marked as a duplicate of this bug. ***
I'll take this.
Assignee: new-network-bugs → gordon
Status: UNCONFIRMED → NEW
Ever confirmed: true
Status: NEW → ASSIGNED
Summary: DNS: problem → DNS: stopping/reloading causes DNS failures?
-> defaults.
Assignee: gordon → darin
Status: ASSIGNED → NEW
Assignee: darin → nobody
QA Contact: benc → networking
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
Whiteboard: dupeme
You need to log in before you can comment on or make changes to this bug.