Every once in a while (time between failures ranges from 1 hour to a few days), Firefox on my laptop suddenly and permanently (until reboot) loses its ability to do DNS lookups. Every page comes up with "Firefox can't find the server at www.foo.com." Other apps (and computers on the network) continue to work fine. It seems random; I haven't been able to correlate it with anything else on the machine. Closing and restarting Firefox doesn't restore its DNS lookup ability, but rebooting does. Googling only turned up the advice to disable IPv6, which didn't help. I'm currently running Firefox 188.8.131.52 on a Dell Inspiron 8600 running XP Home, but it's been an issue since at least 1.5. My only extension is Better Gmail, and I've tried disabling all extensions in the past. I'm at my wit's end - do any geniuses here have a clue?
posted by dfan
on Oct 26, 2007 -
re: Firefox ... lately, I've been having weird DNS issues. I don't recall it ever happened before I switched to firefox, so I assume it's to blame, though that may be a red herring. What happens is this : I have several pages listed in my homepage setting, with each url separated by a '|'. 12 of em to be exact. More than occasionally, anywhere from 1/4 to 1/2 of them come up with a "server cannot be found" error. Sometimes, if I wait for all of the tabs to open, and then try to load the previously not found page, it'll open successfully. Other times, it just doesn't come up no matter how or when I refresh. I've tried resetting my nameserver settings on my router -- both hard-coded nameserver spec. and 'get nameserver information from isp,' but the problem persists.
posted by crunchland
on Jan 18, 2005 -
I have managed to install my beloved Firefox on my "heavily secured" computer at work and told it to use the company proxy server (we can only go through port 80). I'm not supposed to be using anything other than IE, but, well, you understand. The problem is that I can't access any .net domains (.com, .org, .co.uk and any other TLD works as it should) with Firefox, while this is not a problem in IE. Using the IP number of a .net website brings me to the site just fine, so it seems to be a DNS issue, but I have never heard of a TLD requiring its own DNS server or a special port. I can't ask the company IT people as I'm not allowed to use FF in the first place, and the FF support forums have never even answered my question. Any ideas?
posted by Skyanth
on Dec 13, 2004 -