Ubuntu Firefox handles DNS failure poorly
I think this may warrant a bug report.
When the primary DNS server is set to the wrong address, Firefox takes 10 to 15 seconds to look up URLs. The problem does not occur on Windows XP, and appears to be much less severe on Fedora 13 or with Google Chrome.
Steps to reproduce:
1. Set 192.68.0.1 (incorrect value) as the primary DNS and 208.67.220.220 (OpenDNS) as the secondary. In my case this I am using a WRT54GL router with DHCP, so the DNS was determined by the router, and these settings were in the router.
2. Reboot to make sure you are using OpenDNS. Verify the server used by typing nslookup www.google.com .
3. Go to http://
Results
1. The status line displays "Looking up [URL address] ..." for 10 to 15 seconds. This is reproducible.
2. If the primary DNS is set correctly and the computer is rebooted, the problem is solved and the lookup is almost instantaneous. (Primary DNS set to 192.168.0.1 (the modem) instead of 192.68.0.1 in the router; primary DNS in the modem was left at 68.94.156.1 [Southwestern Bell].)
Other diagnostic information
1. Nslookup returns the IP address in 0 to 2 seconds (even if run before Firefox). Thus, the system appears to be handling the lookup much faster than Firefox.
2. Even if nslookup is used immediately before Firefox, Firefox is still slow. Thus, IP address caching does not speed up Firefox.
3. I never observed the problem with Windows XP (I tested on the same machine). Name resolution is almost instantaneous.
4. I have not tested much with other browsers or other OS's, but Google Chrome (Ubuntu) and Fedora 13 (Firefox, live CD) are much faster. Typically 4 seconds, as opposed to 10-15 seconds with Ubuntu Firefox.
Question information
- Language:
- English Edit question
- Status:
- Solved
- For:
- Ubuntu firefox Edit question
- Assignee:
- No assignee Edit question
- Solved by:
- VanillaMozilla
- Solved:
- Last query:
- Last reply: