<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>
Please check the stats of my server in production use.... always cache HITS 11% <br><br>Feb 8 09:42:30 LebolDns pdns_recursor[1970]: Timeout from remote TCP client 109.75.64.121<br>Feb 8 09:42:31 LebolDns pdns_recursor[1970]: Timeout from remote TCP client 109.75.64.121<br>Feb 8 09:42:44 LebolDns pdns_recursor[1970]: Timeout from remote TCP client 109.75.64.121<br>Feb 8 09:42:45 LebolDns pdns_recursor[1970]: Timeout from remote TCP client 109.75.64.121<br>Feb 8 09:43:12 LebolDns pdns_recursor[1970]: stats: 8624720 questions, 918037 cache entries, 78819 negative entries, 11% cache hits<br>Feb 8 09:43:12 LebolDns pdns_recursor[1970]: stats: throttle map: 212, ns speeds: 3373<br>Feb 8 09:43:12 LebolDns pdns_recursor[1970]: stats: outpacket/query ratio 47%, 0% throttled, 0 no-delegation drops<br>Feb 8 09:43:12 LebolDns pdns_recursor[1970]: stats: 1933 outgoing tcp connections, 10 queries running, 84917 outgoing timeouts<br>Feb 8 09:43:12 LebolDns pdns_recursor[1970]: stats: 500083 packet cache entries, 58% packet cache hits<br>Feb 8 09:43:12 LebolDns pdns_recursor[1970]: stats: 51 qps (average over 1804 seconds)<br><br>I have 3Mbps full fiber dedicated for this server and i'm having DNS alerts on my bluecoat (cacheflow)....<br><br>Please advise <br><br><br><br><br><br>> Date: Mon, 7 Feb 2011 11:37:46 +0100<br>> From: bert.hubert@netherlabs.nl<br>> To: maroon_ibrahim@hotmail.com<br>> CC: pdns-users@mailman.powerdns.com<br>> Subject: Re: [Pdns-users] PDNS Recursor on Debian / Low performance !!!URGENT!!!!<br>> <br>> On Mon, Feb 07, 2011 at 09:38:42AM +0000, Maroon Ibrahim wrote:<br>> > all-outqueries 501740<br>> > outgoing-timeouts 352596<br>> > throttled-outqueries 76300<br>> <br>> This mostly tells the story. Your pdns_recursor has problems talking to the<br>> network at sufficient speed. Either this is caused by you requiring too much<br>> bandwidth, or by a firewall that gets upset by all the different UDP<br>> 'sessions' it sees.<br>> <br>> Of 501k queries, 428k did not get answers. 352k were direct timeouts, 76k<br>> were not even sent out by PowerDNS because it had a 'cached timeout'.<br>> <br>> > over-capacity-drops 31945<br>> <br>> You should increase 'max-mthreads' beyond 1024 after you have your network<br>> fixed, you dropped 31945 queries because 1024 were already running.<br>> <br>> Fixing the network needs to happen upstream, this can't be done by PowerDNS.<br>> <br>> Good luck!<br>> <br>> Bert<br> </body>
</html>