[squid-users] Noticeable difference in DNS Service times after upgrade

2015-06-10 Thread Sebastian Goicochea

Hello everyone, I just have a quick question
Is there any difference in how Squid 3.5 measures DNS Service Time 
compared to 2.7 branch?
We monitor this value using SNMP and it has been nearly 0 for months, 
but after the upgrade it went up to 6ms (with 8ms peaks)

All other Service times have varied but apparently they improved


Here's the graphic: http://imgur.com/4pCK3cY
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users


Re: [squid-users] Noticeable difference in DNS Service times after upgrade

2015-06-10 Thread Amos Jeffries
On 11/06/2015 5:16 a.m., Sebastian Goicochea wrote:
 Hello everyone, I just have a quick question
 Is there any difference in how Squid 3.5 measures DNS Service Time
 compared to 2.7 branch?
 We monitor this value using SNMP and it has been nearly 0 for months,
 but after the upgrade it went up to 6ms (with 8ms peaks)
 All other Service times have varied but apparently they improved
 
 
 Here's the graphic: http://imgur.com/4pCK3cY


Not that I know of, but there is both more and less being done.

The more:

* IPv6 support adds an  lookup.

* CVE-2009-0801 protection for intercepted traffic requires A+
lookup in situations which may previously not done any at all.

* hosts without FQDN may now have a .local variant looked up.

The less:

* re-sends of HTTP messages no longer perform full lookups on each
outbound connection attempt. Just one set per message now.

* .local domains no longer have any global DNS lookups. multicast-DNS is
used instead.

Amos

___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users