RE: [squid-users] cache_peer using DNS name

I have not ran into the problem since disabling the IPv6 this morning, using the DNS name for the chace_peer with the name= option set on the line.
Looks like you got it right Amos, thanks a bunch for your help.

Dean

-----Original Message-----
From: Dean Weimer [mailto:dweimer_at_orscheln.com]
Sent: Thursday, April 01, 2010 9:54 AM
To: Amos Jeffries; squid-users_at_squid-cache.org
Subject: RE: [squid-users] cache_peer using DNS name

I don't have IPv6 capability, but on this test system I just did a quick install and Squid does have the default IPv6 setup as does the O/S (FreeBSD 7.2). I will recompile with --disable-ipv6 and see if the problem goes away. Not sure if they have a AAAA record for the hostname, I get a server fail response when trying against the DNS servers I have configured on the system. The Bind DNS servers I am hitting do have IPv6 disabled. I have recompiled Squid with the --disable-ipv6 option and set my cache_peer line back to the domain name. I will let you know if this resolves the problem, after the new configuration is running long enough to know.

-----Original Message-----
From: Amos Jeffries [mailto:squid3_at_treenet.co.nz]
Sent: Wednesday, March 31, 2010 5:17 PM
To: squid-users_at_squid-cache.org
Subject: Re: [squid-users] cache_peer using DNS name

Henrik Nordström wrote:
> ons 2010-03-31 klockan 14:41 -0500 skrev Dean Weimer:
>> I found it listed in 3.0PRE3 bugs, here is the link that I found, it is listed as fixed.
>
> And it is fixed. That was a typo which made Squid always use the name=
> instead of the host when figuring out how to connect to the peer.
> Obvious error, and long time gone (fixed in 2003, long before 3.0 was
> released in 2007).
>

Does the peer have AAAA records and you have no IPv6 connectivity?

This looks like one of the effects of our failover bug. Compounded by
the fact the peer name is looked up so often.

Amos

-- 
Please be using
   Current Stable Squid 2.7.STABLE9 or 3.1.1