Hi Alex, I gave it a try to examine the code. What worries me is that peerDnsRefreshStart() has hard-coded values of 180s and 3600s. I seem to always see the 3600s variant and cannot get any other behavior from squid (but 3min waiting would still be a lot). If the peers are resolved, squid recovers all right from failed connection attempts.
My planed workaround is to have some kind of monitor-service that sends SIGHUP to squid when the VPN connection changes. Squid will forget about the failed DNS lookups and immediately try to resolve the peers, and service is restored in seconds. Hope it works out! Thx, Christoph _______________________________________________ squid-users mailing list [email protected] https://lists.squid-cache.org/listinfo/squid-users
