Re: [squid-users] Very slow initial reply

2014-08-27 Thread Eliezer Croitoru
I have looked at the domain NS and it seems that 2 out of 4 are not responsive at all. If you are interested in clearing out the issue and more advanced dns related issues you can try bind-us...@lists.isc.org list. In the above list there are many dns administrators that can help and consult

Re: [squid-users] Very slow initial reply

2014-08-27 Thread Bruno Guerreiro
idea? Bruno Guerreiro DMSI/IT Instituto Nacional de Estatística Tel: 218440448 - Ext: 1657 - Original Message - From: Eliezer Croitoru elie...@ngtech.co.il To: squid-users@squid-cache.org Sent: Wednesday, 27 August, 2014 7:28:57 AM Subject: Re: [squid-users] Very slow initial

Re: [squid-users] Very slow initial reply

2014-08-27 Thread Amos Jeffries
On 27/08/2014 8:50 p.m., Bruno Guerreiro wrote: Hello. Thanks for your reply. DNS was also my first thought, but what surprises me is that on the same server, nginx or direct are ok, but squid takes almost a minute. Also nslookup and dig work fast. And this happens everytime. But i'll look

Re: [squid-users] Very slow initial reply

2014-08-26 Thread Eliezer Croitoru
Can you try to use dns_v4_first on? Eliezer On 08/26/2014 08:32 PM, Bruno Guerreiro wrote: Hello. Some of our user are complaning about very slow access to some sites. After some tests i've noticed that the time between squid receiving the request, and actually connecting to the site itself

Re: [squid-users] Very slow initial reply

2014-08-26 Thread Cassiano Martin
On my squid box it shows DNS failure. 014/08/26 15:15:09.243 kid1| ModEpoll.cc(139) SetSelect: FD 8, type=1, handler=1, client_data=0, timeout=0 2014/08/26 15:15:09.243 kid1| dns_internal.cc(1362) idnsRead: idnsRead: FD 8: received 55 bytes from 127.0.0.1:53 2014/08/26 15:15:09.243 kid1|