f the TTL from an upstream resolver happens to be
'0', it changes it to whatever positive_dns_ttl is -- even though
that also acts as a ceiling for DNS TTLs.
I think this is partly left over from the old days when Squid always
used the external dnsserver programs. 'dnsserver&#x
;>ttl = Config.positiveDnsTtl;
>>>>if (ttl < Config.negativeDnsTtl)
>>>>ttl = Config.negativeDnsTtl;
>>>>i->expires = squid_curtime + ttl;
>>>
>>> As I read this, if the TTL from an upstream resolver happens to be
>>&
ens to be
'0', it changes it to whatever positive_dns_ttl is -- even though
that also acts as a ceiling for DNS TTLs.
I think this is partly left over from the old days when Squid always
used the external dnsserver programs. 'dnsserver' could only report
TTLs if the O/S had the
TTL from an upstream resolver happens to be '0', it
changes it to whatever positive_dns_ttl is -- even though that also acts as a
ceiling for DNS TTLs.
I think this is partly left over from the old days when Squid always
used the external dnsserver programs. 'dnsserver' coul
'0', it changes it to whatever positive_dns_ttl is -- even though
that also acts as a ceiling for DNS TTLs.
The problem is that this plays havoc with DNS-based load balancers,
which will be '0' more often than other DNS entries by nature. Any
chance of either;
a) havin
