<p dir="ltr">That is useful! Thanks for that!</p>
<p dir="ltr">Federico</p>
<div class="gmail_quote">On 4 Jan 2016 23:13, "bert hubert" <<a href="mailto:bert.hubert@powerdns.com">bert.hubert@powerdns.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Mon, Jan 04, 2016 at 11:04:12PM +0000, Federico Olivieri wrote:<br>
> Hi,<br>
><br>
> Just a question from my side. There is any way to understand, from the<br>
> total count of packet dropped, how many packets have been dropped for<br>
> SERVFAIL?<br>
<br>
Hi Federico,<br>
<br>
We don't drop queries for servfail. We just pass it along. However, with the<br>
following, you can get stats:<br>
<br>
topResponses(10, 2)<br>
<br>
This shows the top-10 servfail responses.<br>
<br>
If you look with dumpStats():<br>
acl-drops 0 latency1-10 0<br>
block-filter 0 latency10-50 0<br>
cpu-sys-msec 14 latency100-1000 0<br>
cpu-user-msec 19 latency50-100 0<br>
downstream-send-errors 0 no-policy 0<br>
downstream-timeouts 0 noncompliant-queries 0<br>
dyn-block-nmg-size 0 queries 7<br>
dyn-blocked 0 rdqueries 7<br>
fd-usage 15 real-memory-usage 7151616<br>
latency-avg100 22.0 responses 5<br>
latency-avg1000 2.2 rule-drop 0<br>
latency-avg10000 0.2 rule-nxdomain 0<br>
latency-avg1000000 0.0 self-answered 0<br>
latency-slow 0 servfail-responses 5<br>
latency0-1 5 trunc-failures 0<br>
uptime 101<br>
<br>
You see 'servfail-responses' counted. The downstream-timeouts metric does<br>
eventually get updated, I just wrote a change that makes this metric react<br>
more quickly.<br>
<br>
Bert<br>
<br>
<br>
<br>
><br>
> Thank You<br>
><br>
> Federico<br>
><br>
> 2016-01-04 18:14 GMT+00:00 bert hubert <<a href="mailto:bert.hubert@powerdns.com">bert.hubert@powerdns.com</a>>:<br>
><br>
> > On Sat, Dec 19, 2015 at 04:34:11PM +0100, bert hubert wrote:<br>
> > > Could be, we have the infrastructure to give insight into that but we<br>
> > don't<br>
> > > make it easy yet:<br>
> ><br>
> > Hi Aleš,<br>
> ><br>
> > As of right now (the packages that are building now), you can do:<br>
> ><br>
> > grepq("3000ms")<br>
> ><br>
> > And get all timeouts. It also shows you which downstream caused the<br>
> > timeout.<br>
> ><br>
> > > grepq("3000ms")<br>
> > Time Client Server ID<br>
> > Name Type Lat. TC RD AA Rcode<br>
> > -67.0 <a href="http://127.0.0.1:44898" rel="noreferrer" target="_blank">127.0.0.1:44898</a> <a href="http://8.8.4.4:53" rel="noreferrer" target="_blank">8.8.4.4:53</a><br>
> > 1853 <a href="http://ds9a.com" rel="noreferrer" target="_blank">ds9a.com</a>. A 3433.1 RD No Error. 1 answers<br>
> > -54.5 <a href="http://127.0.0.1:41892" rel="noreferrer" target="_blank">127.0.0.1:41892</a> <a href="http://8.8.4.4:53" rel="noreferrer" target="_blank">8.8.4.4:53</a><br>
> > 32463 <a href="http://ezdns.it" rel="noreferrer" target="_blank">ezdns.it</a>. A T.O No Error. 0 answers<br>
> > -49.3 <a href="http://127.0.0.1:41892" rel="noreferrer" target="_blank">127.0.0.1:41892</a> <a href="http://8.8.4.4:53" rel="noreferrer" target="_blank">8.8.4.4:53</a><br>
> > 32463 <a href="http://ezdns.it" rel="noreferrer" target="_blank">ezdns.it</a>. A T.O No Error. 0 answers<br>
> > -44.2 <a href="http://127.0.0.1:41892" rel="noreferrer" target="_blank">127.0.0.1:41892</a> <a href="http://8.8.4.4:53" rel="noreferrer" target="_blank">8.8.4.4:53</a><br>
> > 32463 <a href="http://ezdns.it" rel="noreferrer" target="_blank">ezdns.it</a>. A T.O No Error. 0 answers<br>
> ><br>
> > Or use topSlow():<br>
> > > topSlow()<br>
> > 1 <a href="http://ezdns.it" rel="noreferrer" target="_blank">ezdns.it</a>. 3 75.0%<br>
> > 2 <a href="http://ds9a.com" rel="noreferrer" target="_blank">ds9a.com</a>. 1 25.0%<br>
> > 3 Rest 0 0.0%<br>
> ><br>
> > You can also do topSlow(10, 4000) to get everything slower than 4000<br>
> > milliseconds, or even topSlow(10, 4000, 1) which will group everything by<br>
> > tld.<br>
> ><br>
> > Can you let us know if this is what you need?<br>
> ><br>
> > Bert<br>
> ><br>
> ><br>
> > ><br>
> > > > grepq(".")<br>
> > > Time Client ID Name<br>
> > Type Lat. TC RD AA Rcode<br>
> > > -25.0 <a href="http://127.0.0.1:59117" rel="noreferrer" target="_blank">127.0.0.1:59117</a> 13086 <a href="http://ds9a.nl" rel="noreferrer" target="_blank">ds9a.nl</a>.<br>
> > A RD Question<br>
> > > -21.2 <a href="http://127.0.0.1:59117" rel="noreferrer" target="_blank">127.0.0.1:59117</a> 0 <a href="http://ds9a.nl" rel="noreferrer" target="_blank">ds9a.nl</a>.<br>
> > A 0.0 No Error. 0 answers<br>
> > > -20.0 <a href="http://127.0.0.1:59117" rel="noreferrer" target="_blank">127.0.0.1:59117</a> 13086 <a href="http://ds9a.nl" rel="noreferrer" target="_blank">ds9a.nl</a>.<br>
> > A RD Question<br>
> > > -16.2 <a href="http://127.0.0.1:59117" rel="noreferrer" target="_blank">127.0.0.1:59117</a> 0 <a href="http://ds9a.nl" rel="noreferrer" target="_blank">ds9a.nl</a>.<br>
> > A 0.0 No Error. 0 answers<br>
> > > -15.0 <a href="http://127.0.0.1:59117" rel="noreferrer" target="_blank">127.0.0.1:59117</a> 13086 <a href="http://ds9a.nl" rel="noreferrer" target="_blank">ds9a.nl</a>.<br>
> > A RD Question<br>
> > > -11.2 <a href="http://127.0.0.1:59117" rel="noreferrer" target="_blank">127.0.0.1:59117</a> 0 <a href="http://ds9a.nl" rel="noreferrer" target="_blank">ds9a.nl</a>.<br>
> > A 0.0 No Error. 0 answers<br>
> > ><br>
> > > This "knows" about timeouts to backends, but we don't make it easy to<br>
> > "grep" for them.<br>
> > ><br>
> > > Will add this as a feature.<br>
> > ><br>
> > > Bert<br>
> > ><br>
> > > ><br>
> > > > Regards<br>
> > > > Ales<br>
> > > ><br>
> > > ><br>
> > > > On Saturday 19 of December 2015 13:20:35 Federico Olivieri wrote:<br>
> > > > > Hi guys,<br>
> > > > ><br>
> > > > > Nobody has any clue for this? I woukd try to understand why dnsdist<br>
> > shows<br>
> > > > > some dropped packets. There is any debug that can help me to<br>
> > understand why<br>
> > > > > it os happen?<br>
> > > > ><br>
> > > > > Thanks and Merry Christmas!!!<br>
> > > > ><br>
> > > > > Federico<br>
> > > > ><br>
> > > > > On 18 Dec 2015 14:22, "Federico Olivieri" <<a href="mailto:lvrfrc87@gmail.com">lvrfrc87@gmail.com</a>><br>
> > wrote:<br>
> > > > > > Hi all,<br>
> > > > > ><br>
> > > > > > I have a raspberry that is running dnsdist with this configuration:<br>
> > > > > ><br>
> > > > > > newServer{address="<a href="http://192.168.0.3:53" rel="noreferrer" target="_blank">192.168.0.3:53</a>"}<br>
> > > > > > newServer{address="<a href="http://127.0.0.1:5300" rel="noreferrer" target="_blank">127.0.0.1:5300</a>", pool="abuse"}<br>
> > > > > > addPoolRule({"<a href="http://wpad.domain.name" rel="noreferrer" target="_blank">wpad.domain.name</a>"}, "abuse")<br>
> > > > > > webserver("<a href="http://192.168.0.2:8083" rel="noreferrer" target="_blank">192.168.0.2:8083</a>", "supersecret")<br>
> > > > > > addACL("<a href="http://0.0.0.0/0" rel="noreferrer" target="_blank">0.0.0.0/0</a>")<br>
> > > > > > addACL("::/0")<br>
> > > > > > carbonServer('37.252.122.50', 'raspi-836', 30)<br>
> > > > > ><br>
> > > > > > I don't know why, but on webserver I can see some packets dropped<br>
> > from the<br>
> > > > > > primary server and I don't understand the reason why. There is not<br>
> > any<br>
> > > > > > queries rate for that server<br>
> > > > > ><br>
> > > > > ><br>
> > #NameAddressStatusQueriesDropsQPSOutWeightOrderPools0192.168.0.3:53up24108<br>
> > > > > > 6720111127.0.0.1:5300up10100011abuse<br>
> > > > > ><br>
> > > > > > Do you have any idea why there are some dropped packets?<br>
> > > > > ><br>
> > > > > > Also, I added this line of conf. I could see the queries to goolge<br>
> > but I<br>
> > > > > > could see also the queries to a.root server. Seems that the<br>
> > command does<br>
> > > > > > not overwrite the default one. Is it the aspect behaviour?<br>
> > > > > ><br>
> > > > > > newServer {address="192.168.0.3", checkType="A",<br>
> > > > > > checkName="<a href="http://www.google.com" rel="noreferrer" target="_blank">www.google.com</a>.", mustResolve=true}<br>
> > > > > ><br>
> > > > > > Last question: I added the carbon server. I can see the server on<br>
> > > > > > <a href="https://metronome1.powerdns.com/" rel="noreferrer" target="_blank">https://metronome1.powerdns.com/</a> but no one graph is plotted<br>
> > > > > ><br>
> > > > > > Thank you for your time.<br>
> > > > > ><br>
> > > > > > BTW, dnsdist seems very useful and powerful!!!<br>
> > > > > ><br>
> > > > > > Federico<br>
> > > ><br>
> > ><br>
> > > > _______________________________________________<br>
> > > > Pdns-users mailing list<br>
> > > > <a href="mailto:Pdns-users@mailman.powerdns.com">Pdns-users@mailman.powerdns.com</a><br>
> > > > <a href="http://mailman.powerdns.com/mailman/listinfo/pdns-users" rel="noreferrer" target="_blank">http://mailman.powerdns.com/mailman/listinfo/pdns-users</a><br>
> > ><br>
> > ><br>
> > > _______________________________________________<br>
> > > dnsdist mailing list<br>
> > > <a href="mailto:dnsdist@mailman.powerdns.com">dnsdist@mailman.powerdns.com</a><br>
> > > <a href="http://mailman.powerdns.com/mailman/listinfo/dnsdist" rel="noreferrer" target="_blank">http://mailman.powerdns.com/mailman/listinfo/dnsdist</a><br>
> ><br>
> > _______________________________________________<br>
> > dnsdist mailing list<br>
> > <a href="mailto:dnsdist@mailman.powerdns.com">dnsdist@mailman.powerdns.com</a><br>
> > <a href="http://mailman.powerdns.com/mailman/listinfo/dnsdist" rel="noreferrer" target="_blank">http://mailman.powerdns.com/mailman/listinfo/dnsdist</a><br>
> ><br>
</blockquote></div>