vollkommen@xxxxxxx wrote:
I've made one change in squid.conf that seems to cure most of the
problem, with STABLE14-20090411:
cache_peer 127.0.0.1 parent 8123 0 no-query no-digest
no-netdb-exchange default
Interestingly, I was searching about "tunnelReadServer: FD 70: read
failure: (0) Unknown error: 0" when I found the above options on a
Russian forum.
However, it appears URLs with a question mar (e.g.
http://www.ipv6.sixxs.net/forum/?msg=general or
http://ipv6.google.com/advanced_search?hl=en) still causes the same
DNS lookup failure: squid either spits out "ipcacheParse: No Address
records in response to 'www.ipv6.sixxs.net'" in cache.log, or the
brower gets "Unable to determine IP address from host name
"www.ipv6.sixxs.net"", but rarely both. Is this because of
"hierarchy_stoplist cgi-bin ?"? If so, how do I work around it, given
my setup?
Oh, good spotting.
Yes that is likely part of the problem, its purpose is to prevent
dynamic pages being sent to peers. The lack of support for IPv6 in 3.0
is another part.
See my other response to your earlier mail for the ICP part and fix.
Amos
--
Please be using
Current Stable Squid 2.7.STABLE6 or 3.0.STABLE14
Current Beta Squid 3.1.0.7
