![]() echo "nameserver vv.xx.yy.zz" | sudo tee /etc/nf & echo -e "nameserver 8.8.8.8" "\nnameserver 8.8.4.4" | sudo tee -a /etc/nf ![]() Let's assume that your ISP's DNS is vv.xx.yy.zz, so you need to run the following commands to make it as the primary DNS and keeping the Google's DNS as a backup. Although you can keep the Google's DNS as the backup in case your ISP's one fails for some reason. Ask your ISP to give you their DNS address (can be multiple) and add the address as the nameserver. One very important thing to note here, we are using google's DNS which is not ideal, you should use your ISP's DNS here. In this way we have a working name resolver that will resolve the hostnames we give into IP addresses. This command will insert the text "nameserver 8.8.8.8" into the "/etc/nf" file and display the text on the screen too. We are basically setting the Google's free DNS server (8.8.8.8) as the nameserver. But surprisingly in your case the resolvconf is not installed so we have to manually update the /etc/nf file.Įcho "nameserver 8.8.8.8" | sudo tee /etc/nf In Ubuntu 12.04 the Network Manager package provides the network related functionality (rather than the old networking program), with the resolvconf (and dnsmasq to some extent) program providing the mass DNS functionality. As there was no DNS nameserver entries in the /etc/nf file so the name resolution was failing while pinging by hostname to hosts outside your /etc/hosts entries. # newer versions of some applications which may provide useful features.The problem is purely related to DNS. ![]() # extensively as that contained in the main release, although it includes software from this repository may not have been tested as # multiverse WILL NOT receive any review or updates from the Ubuntu # team, and may not be under a free licence. # review or updates from the Ubuntu security team. Also, please note that software in universe WILL NOT receive any software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu # Major bug fix updates produced after the final release of theĭeb-src precise-updates restricted main multiverse universe #Added by software-properties W: Duplicate sources.list entry precise/main i386 Packages (/var/lib/apt/lists/_sgringwe_beatbox_ubuntu_dists_precise_main_binary-i386_Packages)Ĭontents of /etc/apt/sources.list: # deb cdrom:/ oneiric main restrictedĭeb-src precise main restricted #Added by software-propertiesĭeb-src precise multiverse universe #Added by software-properties W: Duplicate sources.list entry precise/main i386 Packages (/var/lib/apt/lists/_nemequ_sqlheavy_ubuntu_dists_precise_main_binary-i386_Packages) They have been ignored, or old ones used instead. W: Failed to fetch Unable to connect to :http: Unable to connect to :http: Ĭould not connect to :80 (91.189.88.33). Here is the output from sudo apt-get update: sudo apt-get update Updates from the Update Manager worked fine and I could download some things (mutter) from the Software Center without incident, which makes me think I can connect to some subset of the Ubuntu servers (however, several other Ubuntu servers-like extras-and some canonical servers are listed as 'unable to connect'). as well as the "main server" (wherever that is) and they all yield the same result: I can't connect to any software sources.Īdditionally, I'm fairly certain the problem stems from the upgrade from 11.10->12.04 I performed this morning, as updates worked immediately before. ![]() Additionally, I've tried several different servers in Europe and the U.S. I realize there are dozens of "apt-get update: failure to fetch" questions (I read through all I could find), but my present circumstance is unique to 12.04 and it affects all sources not just launchpad.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |