[squid-users] Re: DNS Queue Remains Filled Issue!

Hi,

Thanks for response & sorry for late reply coz i have just recovered from
fever....

>Are they the same ones constantly? even after the timeout is reported to
clients?

No, the ids remains changing but all the clients keep on receiving timeout
message. Here is first output of
 
#squidclient mgr:idns
HTTP/1.0 200 OK
Server: squid/3.1.20
Mime-Version: 1.0
Date: Mon, 25 Feb 2013 06:05:19 GMT
Content-Type: text/plain
Expires: Mon, 25 Feb 2013 06:05:19 GMT
Last-Modified: Mon, 25 Feb 2013 06:05:19 GMT
X-Cache: MISS from localhost
X-Cache-Lookup: MISS from localhost:3128
Via: 1.0 localhost (squid/3.1.20)
Connection: close

Internal DNS Statistics:

The Queue:
                       DELAY SINCE
  ID SIZE SENDS FIRST SEND LAST SEND
------ ---- ----- ---------- ---------
0xe1c6 42 5 40.115 10.043
0x4986 32 3 15.175 5.043
0xec04 46 5 31.429 1.043
0xdf69 31 7 107.340 37.043
0x0142 35 7 107.810 37.043
0x8f6d 33 7 97.736 27.043
0xa9c0 34 5 47.918 17.043
0x7f72 43 8 128.336 18.043
0xcbdd 31 8 113.573 3.043
0x171e 42 7 108.646 38.043
0x0322 40 1 3.502 3.502
0xb37c 41 7 104.886 34.043
0x92b0 33 5 44.396 14.043
0xad63 35 5 39.893 9.043
0x7fdc 36 4 24.085 4.043

Nameservers:
IP ADDRESS # QUERIES # REPLIES
---------------------------------------------- --------- ---------
8.8.8.8 1415 1280
116.71.241.216 123 78

Rcode Matrix:
RCODE ATTEMPT1 ATTEMPT2 ATTEMPT3
    0 1357 0 0
    1 0 0 0
    2 0 0 0
    3 1 0 0
    4 0 0 0
    5 0 0 0

Here the output after some time
#squidclient mgr:idns
HTTP/1.0 200 OK
Server: squid/3.1.20
Mime-Version: 1.0
Date: Mon, 25 Feb 2013 06:07:51 GMT
Content-Type: text/plain
Expires: Mon, 25 Feb 2013 06:07:51 GMT
Last-Modified: Mon, 25 Feb 2013 06:07:51 GMT
X-Cache: MISS from localhost
X-Cache-Lookup: MISS from localhost:3128
Via: 1.0 localhost (squid/3.1.20)
Connection: close

Internal DNS Statistics:

The Queue:
                       DELAY SINCE
  ID SIZE SENDS FIRST SEND LAST SEND
------ ---- ----- ---------- ---------
0x4404 30 7 95.739 25.606
0x2cd5 47 6 51.019 0.574
0x98aa 52 4 26.420 5.575
0x47e2 44 7 96.915 26.606
0x0202 49 7 97.356 26.606
0x6562 35 7 81.892 11.575
0x48bc 34 7 83.672 12.575
0xfe15 35 7 108.975 38.641
0x638c 33 7 104.046 33.606
0x7968 43 1 4.246 4.246
0x817e 35 8 115.102 4.575
0xbe90 31 7 104.791 34.607
0x9db5 33 5 40.197 9.575

Nameservers:
IP ADDRESS # QUERIES # REPLIES
---------------------------------------------- --------- ---------
8.8.8.8 1472 1280
116.71.241.216 182 78

Rcode Matrix:
RCODE ATTEMPT1 ATTEMPT2 ATTEMPT3
    0 1357 0 0
    1 0 0 0
    2 0 0 0
    3 1 0 0
    4 0 0 0
    5 0 0 0

>Also try to debug why DNS is not responding immediately. Command line
>from the Squid box:
> dig -t AAAA example.com @<your DNS server>
> dig -t A example.com @<your DNS server>

Dig command shows that the dns are working fine, also the https queries are
working well.

--
View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/DNS-Returned-Timeout-Issue-tp4658603p4658692.html
Sent from the Squid - Users mailing list archive at Nabble.com.