W dniu 28.04.2017 o 11:00, mbaltruschat pisze:
Hello everybody,
i am trying to migrate my old squid 2.7 to 3.5 and are getting stuck, the
new proxy is very slow, requests need very long until they open, i guess ist
a name resolution problem, because the proxy cant resolve internet domain
names by itself, the name resolution is done by the parent proxy of our
Network Provider. If i look at the statistics by "mgr:info" i see that the
median Service times for dns are around 30 seconds. I guess the old 2.7 just
"ignored" the name resolution because i didnt give him a nameserver to use
and although didnt configure dnshelper.
How can i configure squid not to resolve the names by itself?
Many thanks in advance
Best regards
M. Baltruschat
--
View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-proxy-without-name-resolution-for-internet-adresses-behind-parent-proxy-tp4682225.html
Sent from the Squid - Users mailing list archive at Nabble.com.
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users
Hi,
By "by itself" you ment squid-cache or squid host machine?
I'm using dnsmasq along with squid on the same machine. Dnsmasq has 250
cache enabled and neg-cache disabled and 4-6 DNS configured. AFAIR
dnsmasq asks all configured DNS at once an replies if any of them reply.
But in mgr:dns, it is still squid asking 127.0.0.1.
By the way, what's going on in mgr:dns in your squid-cache? If it's name
resolution problem, it will be there. If your OS uses resolf.conf order,
than it is possible that at list 1st DNS server has problem and you will
see than in mgr:dns stats.
--
Pozdrawiam, Remik
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users
