First, let me say that using the suggestion in #18 about hard coding the DNS fixed the problem for me.
I have a laptop with a 32-bit AMD Sempron processor that I wiped and did a full, fresh install of Ubuntu Lucid Lynx. I have added some 3rd party repositories in my /etc/apt/sources.d/ directory. I am on a home wireless network 802.11g with WPA2 + PSK. My router is a 2Wire Residential Gateway device that acts as DSL modem, wireless router, firewall, and is also where our AT&T U-Verse television comes in the house. I do not have a proxy server. By default, Ubuntu was using the RG itself as the DNS server which is supposed to work just fine. It does work in almost all cases. It doesn't work for apt-get for some reason. I was able to log on to my RG's web interface and get the DNS servers that it was using. I then setup my network connection to use those instead. That fixed it. But, why is this necessary? Also, LTS? I think you've found a new scenario to add to your QA testing. -- Apt has strange network errors when updating indexes. https://bugs.launchpad.net/bugs/574886 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
