Ty. I checked the following
https://www.squid-cache.org/Doc/config/netdb_filename/
<https://www.squid-cache.org/Doc/config/netdb_filename/>, and asked google.
“
# {cache_peer …. no_netdb_exchange } already set earlier
netdb_filename none
pinger_enable off
Icp_port 0 #seems to be default value
“
And this issue persists. It seems that NO squid.conf could help with the DNS
leak issue.
Q1: So, does Squid netdb work on the IP level? In that way, squid has unclear
ACLs that bring up invisible communications.
Q2: Do I have to compile squid from the source code without benefit of
automatic community upgrade ? This is really a less preferable option for most
users.
Is there a higher version of squid that comes up with a powerful conf ?
>>>
>>> FWIW, if I have access to a full debugging log collected while reproducing
>>> the problem, I may be able to tell you what causes DNS lookups in your
>>> specific environment. I discourage Squid admins from studying debugging
>>> logs because they are meant for Squid developers and can be very misleading.
We can only confirm issues and observe callees from logs. _______________________________________________
squid-users mailing list
[email protected]
https://lists.squid-cache.org/listinfo/squid-users
