[squid-users] dns failover failing with 3.4.7

[Amos Jeffries]

On 28/07/2015 8:38 a.m., Mike wrote:
> Running into an issue, using the squid.conf entry
> dns_nameservers 72.x.x.x 72.x.y.y
> 
> These are different servers (under our control) for the purpose of
> filtering than listed in resolv.conf (which are out of our control, used
> for server IP routing by upstream host).
> 
> The problem we found like this weekend is if the primary listed dns
> server is unavailable, squid fails to use the secondary listed server.
> Instead it displays the "unable to connect" type messages with all
> websites.

Details please. How do you know the secondary is not even being tried?

What is Squid getting back from the primary when its "down" ?
 or just dns_timeout being hit?

Add this to squid.conf to get a cache.log trace of the DNS activity:
  debug_options 78,6


Amos