David Timms wrote: > Michael Stenner wrote: >> On Sun, Apr 02, 2006 at 03:33:42PM +1000, David Timms wrote: >>> OK, the machine tries to directly dns lookup the address of the AAAA >>> record of fedora.redhat.com, then A of the same. Within our network, >>> only the proxy machine is allowed to do this, so yum never gets dns >>> answers. >> >> Are you doing ftp or http? > it's using default fedora-updates.repo etc. > mirrorlist=http://fedora.redhat.com/downlo ....etc > proxy=http://192.168.2.2:80/ > > I think there is a mix of ftp and http inside that mirrorlist. > >> In grepping through urllib2.py, I see >> where the ftp code does a lookup, but I don't see where one happens >> for http. > Maybe it's in the code to get the mirrorlist ? > >> Now, many proxies don't handle http byteranges well (a >> feature yum uses and a reason we generally recommend ftp behind a >> proxy) so you may be SOL. If it's a dns problem that's getting you, >> can you plug in the IP address directly? > for both tests in fedora-updates.repo: changed mirrorlist= > fedora.redhat.com to ip from dig: 209.132.177.50 > note: the baseurl is commented out (default)! > ... > > On fedora forum I found a post where someone was messing with there > environment variables (and then needing to do that in the root > environment) to get proxy stuff to work. This may have been telling the > machine it had to use a proxy no matter what!. I would have assumed the > only thing needed was the proxy value in the .repo file ? I noticed that FC5 test update to yum-2.6.1-0.fc5 mentioned some proxy items. I installed this, and with the yum.conf proxy setting enabled (to an ip number), and dns disabled, I can now update with yum / pup without any problem (on two machines). Thanks, for these subtle advances, DaveT.
