apt-get has the problems to resolve address

[pemadorje]

@ThatBum

Tested on Comcast this weekend and there were no issues, no "wicked" errors, nothing.... apt-get updated as it should.

So it does point to an issue with my router or ISP but it's still odd that I never experienced this in Karmic.


Next, I am curious to try "newb85's" suggestion.

http://ubuntuforums.org/showthread.php?t=1475399&page=2
post #17.

[ThatBum]

@ThatBum
http://ubuntuforums.org/showthread.php?t=1475399&page=2
post #17.

HOLY GOD IT WORKED!

Thank you 6.02x10^23 times!

Well, actually, I didn't use my ISP's DNS, I decided to use OpenDNS. But hey! No more problems with apt-get update!

This must be fixed in some kind update, as many people are experiencing it.

Again, thank you for finding it.

[pemadorje]

Cool!Worked for me also, using OpenDNS.

[ThatBum]

Hey, it seems that there is all sorts of problems with DNS here. Not OpenDNS specifically, I shall describe my problem (which I have fixed).

Again, it has to do with my router. The IP of the gateway fr this router is 192.168.1.254. But, it is also accessible through gateway.2wire.net, which is used for places that are not external sites (they are driven by the router), but it USES the Internet, for example, the router's built-in firmware update function. While trying to do just that, Firefox said it didn't exist. I tried pinging it, and ping said it didn't exist.

I fixed this by going into my /etc/hosts and putting this in:

# Lookup for router
192.168.1.254 gateway.2wire.net

Now it works perfectly. Before Lucid, it worked without modification.

So the whole thing is decidedly not a bug in apt. It appears to be some problem with DNS lookups. It doesn't seem to discriminate between external and internal (private) IPs. A very strange problem indeed.

I got the idea from this, a guy who has a similar problem in XP, of all things.

Too lazy to go tell launchpad about this, and I'm starting to think I'm becoming a nuisance there.

[pemadorje]

@ThatBum

You may be on to something. I'm not much of a "network guy" and I don't know if this is related to what you're describing.... but I also had an issue after applying the solution of changing my DNS.

After the change, I wasn't able to access my samba shares with my usual url (smb://hostname/share)... Once I changed it to smb://ipaddress/share, it started working again.

[evencoil]

Again, it has to do with my router. The IP of the gateway fr this router is 192.168.1.254. But, it is also accessible through gateway.2wire.net, which is used for places that are not external sites (they are driven by the router), but it USES the Internet, for example, the router's built-in firmware update function. While trying to do just that, Firefox said it didn't exist. I tried pinging it, and ping said it didn't exist.

I fixed this by going into my /etc/hosts and putting this in:

# Lookup for router
192.168.1.254 gateway.2wire.net

Now it works perfectly. Before Lucid, it worked without modification.

I have the same router and your solution worked for me. Thanks! Remember to restart polipo (say if you have Tor installed):

sudo service polipo restart

[ThatBum]

Thanks! Remember to restart polipo (say if you have Tor installed)

My bandwidth is too crap to use Tor effectively, as a client or a relay, but that's good to know I guess, because I do run Tor on my other machine that's on cable.

[evencoil]

Well it worked for a while--then suddenly returned to the old behavior. Hmm...

[ThatBum]

Well it worked for a while--then suddenly returned to the old behavior. Hmm...

Odd, the DNS shouldn't just change itself...if you're using your ISP's DNS, try using a public DNS, for example, Google's at 8.8.8.8 and 8.8.4.4.

[evencoil]

I think it was due to the symptoms being spotty to begin with...so a solution that looked like a solution wasn't really.

In any case using Google's DNS server works great, thanks!