Hi Frank,
On 12/08/2019 10:27 pm, Lichtnau Frank wrote:
Hi,
I can confirm that we have the same problems under debian buster like
Chris call “dnsdist 1.4 and Debian buster”.
https://mailman.powerdns.com/pipermail/dnsdist/2019-August/000601.html
Thanks for the feedback, this is very helpful
Hi Remi!
Am 11.08.2019 um 18:26 schrieb Remi Gacogne:
> Hi Klaus,
>
> On 8/10/19 10:30 PM, Klaus Darilion wrote:
>> I had similar results. Starting 4 listening threads and 4 receivers
>> threads (by adding the same backend 4 times) boosted my performance -
>> almost linear.
>
> Similar in terms
Hi,
I am running dnsdist 1.4.0-rc1 and I am seeing something odd. As a test I
have the following rule configured.
addAction(MaxQPSIPRule(2, 32, 48), DelayAction(500))
and I run 100 queries at 10 per second and my statistics from my client are
as follows:
Statistics for data/input/input1: min =
Hi,
I'm running dnsdist inside a virtualized host, which has anycasted IP's and
out-of-band IP's.
Using nc I can reach my carbon server BUT have to define the source IP.
Now I wish to have dnsdist sent data to metronome.
So I assumed using "setLocal" would define the main IP, and so set the
ou
Hi,
This message is not dnsdist specifically, but about metronome.
Still I though this channel would be the most appropriate.
I just wrote an rc.d script for the metronome port in FreeBSD.
If you happen to be interrested in both, then please review
https://bugs.freebsd.org/bugzilla/show_bug.cgi
Hi Remi,
I think, it has to be with 'high latencies'.
I have:
- 1 pool (winmls) for windows-ad-dns-queries
- 1 pool (mls) for rest of our internal domain
- and a dns-forwarder (with 3 listener) for external dns-queries.
The pools work fine with latencies of 0.3 - 0.8 The single dns-forwarder ha
Hi,
I'd like to know where I should submit a feature request and what that
process might be?
Thanks,
brian
--
Brian M. Sullivan
Senior Staff Security Intelligence Engineer
bsulli...@lookout.com | www.lookout.com
___
dnsdist mailing list
dnsdist@ma
