Ubuntu Firefox appears to be using different timeout or retry options than the other browser/OS combinations. I can post logs if anyone wants, but a summary should suffice.
If the primary server is 192.68.0.1 (wrong) but the secondary server is correct,
nslookup -d2 www.google.com
shows that it queries both servers, and it returns results immediately.
nslookup -d2 www.google.com 192.68.0.1 [or any nonexistent server]
shows three attempts with 5 second timeouts, followed by failure.
Firefox shows retries and timeouts total 15 seconds, followed by success. I speculate that it's using default timeout of 5 seconds, with two retries, before using another server.
Google Chrome or Fx on Fedora live CD shows (retries?) and timeouts, totaling 5 seconds, followed by success.
OK, inasmuch as this depends on an incorrect setup, it's a minor problem.
Ubuntu Firefox appears to be using different timeout or retry options than the other browser/OS combinations. I can post logs if anyone wants, but a summary should suffice.
If the primary server is 192.68.0.1 (wrong) but the secondary server is correct,
nslookup -d2 www.google.com
shows that it queries both servers, and it returns results immediately.
nslookup -d2 www.google.com 192.68.0.1 [or any nonexistent server]
shows three attempts with 5 second timeouts, followed by failure.
Firefox shows retries and timeouts total 15 seconds, followed by success. I speculate that it's using default timeout of 5 seconds, with two retries, before using another server.
Google Chrome or Fx on Fedora live CD shows (retries?) and timeouts, totaling 5 seconds, followed by success.
OK, inasmuch as this depends on an incorrect setup, it's a minor problem.