[squid-users] squid not liking dnscache for some hosts?

[Amos Jeffries]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 8/10/2014 6:03 a.m., Jason Haar wrote:
> Hi there
> 
> We have CentOS-6 servers running the default squid-3.1.10 with
> dnscache on 127.0.0.1 as the local dns server. It's been working
> fine but we've just had reports that people couldn't reach urls on 
> dl.dropboxusercontent.com
> 
> On the proxy itself, "nslookup dl.dropboxusercontent.com" worked
> fine - returning several IP addresses (just like google and all
> other Cloud service providers do), but squid returns a 404 on any
> page in it (X-Squid-Error: ERR_DNS_FAIL 0). It hangs and sniffing
> made me think it was hanging on the DNS lookup part. I then edited
> /etc/resolv.conf and pointed at some Microsoft DNS servers we have
> (which our dnscache just forwards to anyway) and the problem was
> solved.

Squid 3.1+ are IPv6 enabled. Unfortunately AAAA lookup for
dl.dropboxusercontent.com returns a positive CNAME result with
indication that there are no IP addresses.

This problem should be resolved by Squid-3.2 or later. Please upgrade,
preferrbley to the latest stable, which today is 3.4.8.

Amos

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (MingW32)

iQEcBAEBAgAGBQJUNCjaAAoJELJo5wb/XPRjY1YH/jrqBYgmf4am7g6us66pM5fA
c1d+GAisy5L9lQzFEmObroo7bQNbo2SyiafqAprmvw6gvPx4AAfsnsA3hsSZTEh3
IAk0gAAAeaLycBHPlH69oJ7BSeCqKePQ3GV8iMu6MU/c5S3X+V7RBoCSasvhPK0r
MA0jC38BFTBAKDsUJj1cwPVw0ZreWK+hD7Uqf+HAHtgpY+OZguEurzklTlronjui
9nOJTK7OOwajqGfOaDEbsjing1m9RL+QKu+aPbTW2Vo06VMPGW/CGx14xYzkA5sn
u0KBoEQtZTXENhhD06D3r5QYDwyzIBJPzGPn7LQGt5AH79hxYG/R/h4uBBC0a4E=
=WV73
-----END PGP SIGNATURE-----