This situation often appears on my machine and gives you some problems from time to time. But there are times when it's better to wait. or switch the engine to Baidu, it will make sense.
The problem is very annoying. On the internet to find out that the firewall ah, such as problems. But the problem is often seen when you get it. Just a good look at the information or found the problem, I feel this head is really stupid.
Assume that you are pinging other hosts. Local address and other address after all no problem, that should be the DNS domain name resolution is a problem.
To view the DNS domain name resolution configuration file:
$cat/etc/resolv.conf
My message, for example, is this:
# Dynamic resolv.conf (5) file for glibc resolver (3) generated by resolvconf (8)
# do not EDIT this FILE by HAND--YOUR changes'll be overwritten
NameServer 127.0.0.1
The DNS address should be followed after the nameserver. And here I am the local loopback address. Change it to a DNS address, O,
$sudo vi/etc/resolv.conf
NameServer 8.8.8.8 (free DNS server address provided by Google)
The problem was temporarily conquered. But perhaps after you restart you will find that the same problem has occurred again, open the file/etc/resolv.conf when we last changed the address was reset to the original appearance.
So we need to do some work:
$sudo Vi/etc/resolvconf/resolv.conf.d/head
The same, in the open file add: nameserver 8.8.8.8
After saving the problem will be conquered!
Fix an issue where the Firefox browser in Ubuntu always prompts you not to find the server