Closed
Bug 790507
Opened 13 years ago
Closed 10 years ago
After a period of time the Firefox DNS resolver appears to stop functioning
Categories
(Core :: Networking: DNS, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: dlong500, Unassigned)
Details
Attachments
(2 files)
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.9 (KHTML, like Gecko) Chrome/23.0.1261.0 Safari/537.9
Steps to reproduce:
Open and use Firefox for a period of time (maybe an hour, maybe two days) usually with a dozen or more tabs
Actual results:
Eventually, DNS requests begin to fail with a "Server not found" message. For example, if I try to load "http://www.google.com" I receive a "Server not found" message, but if I ping www.google.com in the console and use the IP address it returns I can load Google just fine using "http://74.125.228.50/". The same applies to other websites as well. This issue is local to Firefox, however, as I can use Chrome or IE normally during this time. This has been a regular issue for me for at least a couple years, and quite frankly my normal course of action is to kill the Firefox process and then reopen it to regain my session and start using it again normally. I usually have to do this at least once every couple days. I've looked into bug 692260, but upon testing it doesn't seem to be the same issue. The closest bug actually appears to be bug 84580, but given that was back in 2001 I'm not sure it helps to revive something that old.
Expected results:
Firefox should function normally (resolve DNS requests) without having to restart it every day or so.
| Reporter | ||
Comment 1•13 years ago
|
||
| Reporter | ||
Comment 2•13 years ago
|
||
| Reporter | ||
Comment 3•13 years ago
|
||
Nobody has any ideas? I'm happy to give any additional info or perform any tests that can narrow down the problem.
Comment 4•10 years ago
|
||
this got lost. sorry. still an issue? reopen if so - we can get an http log
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•