[dnsdist] Marking downstream Unexplained

Federico Olivieri lvrfrc87 at gmail.com
Tue Feb 16 15:39:22 UTC 2016


Hi guys,

It is happen for me as well on 2 different dnsdist with 3 pdns recursor
behind them. There is any way to debug this problem from pdns recursor side?

Federico
On 16 Feb 2016 15:11, "Remi Gacogne" <remi.gacogne+dnsdist at powerdns.com>
wrote:

> Hi Alejandro,
>
> > Can I enable verbose for loggin??
>
> Unfortunately we are not logging more information regarding health check
> failures, even at verbose level. That's mostly because it might fill up
> your logs very quickly otherwise.
>
> Based on the messages you posted, only one health check fails and the
> next ones are fine. So basically, dnsdist sent a UDP query and
> either did not get any response at all in less than one second, or the
> response was invalid:
> - complete garbage or
> - response ID not matching the query ID or
> - QR flag not set or
> - ServFail or
> - NXDomain or Refused (only considered an error if you have set
> mustResolve to true for this backend).
>
> If you don't have a lot of traffic you might be able to see what happen
> by using tcpdump.
>
> Perhaps we should add an option to consider a backend as down only after
> several checks failed in a row. Maybe some counters for health check
> failures might help too.
>
> --
> Remi Gacogne
> PowerDNS.COM BV - https://www.powerdns.com/
>
>
> _______________________________________________
> dnsdist mailing list
> dnsdist at mailman.powerdns.com
> http://mailman.powerdns.com/mailman/listinfo/dnsdist
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.powerdns.com/pipermail/dnsdist/attachments/20160216/f8d60fa3/attachment.html>


More information about the dnsdist mailing list