Normally, I use Mozilla on my laptop when it's connected to the network. When I take my primary network interface (eth0) down, do other stuff while disconnected, then come back and plug back into the network, and bring the interface back up, Mozilla fails to resolve hostnames from then on. Normally when I'm disconnected I don't use Mozilla at all, but I do leave it running. Rebooting Mozilla fixes the problem. Other applications like GNU Emacs and X-Chat are fine in this situation, so I believe it's a Mozilla bug. I'm using the Mozilla packages (0.9.1-4) from Debian sid, on powerpc-debian-linux-gnu. By the way, thanks for all the great work on Mozilla!

related: bug 64857, bug 88144

This is a dupe, but before I mark it, can you tell me if ip-address only URL's fail after you turn ethernet back on?

Reporter(walters@cis.ohio-state.edu): Can you answer Benjamin Chuang question ?

Hm, I thought I added more information to this bug. Anyways, it does correctly connect to URIs containing an IP address after I take the network interface down, then bring it up again.

Thanks for your answer ! marking as dupe of bug 64857 *** This bug has been marked as a duplicate of 64857 ***

Do you know if your network uses DHCP? The reason I ask, is that if I understand mozilla and your situation correctly, if you were to lauch (caching DNS servers), if you went up and down, you should still be able to see those DNS servers when you bring your interface UP again.