RE: DNS

i guess this helps you, Henrik has already answered today:

sslReadServer is not entirely normal. It is seen if the origin server
aborts the SSL connection, and this should not normally happen on
legitime requests.

/*
idnsCheckQueue giving up is more or less normal. It is seen when Squid
is asking for a DNS name where no DNS servers are answering for the
zone.
*/

--
Henrik Nordstrom
Squid hacker
Ronald Warner wrote:
> 
> I have numerous entries like these in my cache.log
> 
> Jun  8 13:15:09 linux9 squid[3986]: sslReadServer: FD 164: read failure:
(104) Connection reset by peer
> Jun  8 13:16:23 linux9 squid[3986]: sslReadServer: FD 93: read failure:
(104) Connection reset by peer
> Jun  8 13:25:48 linux9 squid[3986]: idnsCheckQueue: ID 2c66: giving up
after 20 tries and 125.8 seconds
> Jun  8 13:29:19 linux9 squid[3986]: idnsCheckQueue: ID 2cfe: giving up
after 20 tries and 130.4 seconds
> 
> what are sslReadServer and idnsCheckQueue?  What do they do
> and is it "normal" to get these?
> 
> Thanks in advance
>-----Original Message-----
>From: Samir [mailto:samirfarooq@sat.net.pk]
>Sent: Monday, June 12, 2000 5:42 PM
>To: squid-users@ircache.net
>Subject: DNS
>
>
>i am getting a lot of these in my cache.log
>
>idnsCheckQueue : ID 760e : giving up after 20 tries and 113 sec
>(average)
>idnsCheckQueue : ID 760f : giving up after 20 tries and 113 sec
>(average)
>idnsCheckQueue : ID 7611 : giving up after 20 tries and 113 sec
>(average)
>idnsCheckQueue : ID 7612 : giving up after 20 tries and 113 sec
>(average)
>
>my squid is getting the entries of DNS sever from resolve .conf
>
>