Firefox unable to do dns lookup on first click

Asked by Steve Sauls

I have been noticing that when clicking links in firefox it fails to do the dns lookup and gives you the web page that the site could not be found and you just simply have to click retry and it works. This only happens with my Ubuntu 12.04 machines.

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu firefox Edit question
Assignee:
No assignee Edit question
Solved by:
Steve Sauls
Solved:
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said :
#1

Can you give the output of:

lsb_release -a; uname -a; apt-cache policy firefox

Thanks

Also, do other browsers do the same?

Revision history for this message
Steve Sauls (steve.sauls) said :
#2

No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 12.04 LTS
Release: 12.04
Codename: precise
Linux steve-Aspire-7560 3.2.0-25-generic-pae #40-Ubuntu SMP Wed May 23 22:11:24 UTC 2012 i686 athlon i386 GNU/Linux
firefox:
  Installed: 13.0+build1-0ubuntu0.12.04.1
  Candidate: 13.0+build1-0ubuntu0.12.04.1
  Version table:
 *** 13.0+build1-0ubuntu0.12.04.1 0
        500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main i386 Packages
        500 http://security.ubuntu.com/ubuntu/ precise-security/main i386 Packages
        100 /var/lib/dpkg/status
     11.0+build1-0ubuntu4 0
        500 http://us.archive.ubuntu.com/ubuntu/ precise/main i386 Packages

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#3

Try:

echo "nameserver 8.8.8.8" | sudo tee /etc/resolv.conf > /dev/null

Is it ok then?

Revision history for this message
Steve Sauls (steve.sauls) said :
#4

Dont want to change my resolv.conf file. Right now it is working fast. Maybe it is not the machine and it is the internet provider. For right now I will keep watching it. Thanks for the assistance.

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#5

It's not a point of wanting to change it, it's TESTING to see if your current DNS is causing the issue. It's called 'isolating the issue'