address='192.168.0.2', maxCheckFailures=5, checkInterval=5,
qps=1000, order=6})
Server Load Balancing Policy
setServerPolicy(leastOutstanding)
Regards,
Rais
-Original Message-
From: Klaus Darilion
Sent: Thursday, March 24, 2022 12:38 PM
To: Rais Ahmed ; dnsdist@mailman
@mailman.powerdns.com
Betreff: Re: [dnsdist] dnsdist[29321]: Marking downstream IP:53 as 'down'
Hello Rais,
i noticed that you are increasing nf_conntrack_max. I am not sure how the
backend servers are connected,
but i suggest not to use connection tracking/NAT at all. You can use for
example dedicated
ecs are same on all three servers, are we doing something
wrong?
Regards,
Rais
-Original Message-
From: Klaus Darilion
Sent: Thursday, March 24, 2022 12:38 PM
To: Rais Ahmed;dnsdist@mailman.powerdns.com
Subject: AW: [dnsdist] dnsdist[29321]: Marking downstream IP:53 as 'down
ais
-Original Message-
From: Klaus Darilion
Sent: Thursday, March 24, 2022 12:38 PM
To: Rais Ahmed ; dnsdist@mailman.powerdns.com
Subject: AW: [dnsdist] dnsdist[29321]: Marking downstream IP:53 as 'down'
Have you tested how many Qps your Backend is capably to handle? Fi
> -Ursprüngliche Nachricht-
> Von: dnsdist Im Auftrag von
> Rais Ahmed via dnsdist
> Gesendet: Mittwoch, 23. März 2022 22:02
> An: dnsdist@mailman.powerdns.com
> Betreff: [dnsdist] dnsdist[29321]: Marking downstream IP:53 as 'down'
>
> Hi,
> Thanks
Server({address="10.50.50.36", source="ens192", pool="ns1", checkType="A",
checkType=DNSClass.IN, checkName="www.x.net.", mustResolve=true})
--ns2 infoblox
newServer({address="10.50.51.52", source="ens192", pool="ns2", checkType="A",
checkType=DN
ehalf of Willis,
Michael via dnsdist
Sent: Wednesday, March 23, 2022 5:27 PM
To: dnsdist@mailman.powerdns.com ; Rais Ahmed
Subject: Re: [dnsdist] dnsdist[29321]: Marking downstream IP:53 as 'down'
Bump...
I am personally interested in this as well. I'm trying to something similar
al
sdist] dnsdist[29321]: Marking downstream IP:53 as 'down'
Hi,
Thanks for reply...!
We have configured setMaxUDPOutstanding(65535) and still we are seeing backend
down, logs are showing frequently as below.
Timeout while waiting for the health check response from backend 192.168.1.1:5
r Subject line so it is more specific than "Re:
Contents of dnsdist digest..."
Today's Topics:
1. dnsdist[29321]: Marking downstream IP:53 as 'down' (Rais Ahmed)
2. Re: dnsdist[29321]: Marking downstream IP:53 as 'down'
(Remi Gacogne)
-
Hi,
> We have configured dnsdist instance to handle around 500k QPS, but we
> are seeing downstream down frequently once QPS reached above 25k. below
> are the logs which we found to relative issue.
>
> dnsdist[29321]: Marking downstream server1 IP:53 as 'down'
>
> dnsdist[29321]: Marking downstr
Hi,
We have configured dnsdist instance to handle around 500k QPS, but we are
seeing downstream down frequently once QPS reached above 25k. below are the
logs which we found to relative issue.
dnsdist[29321]: Marking downstream server1 IP:53 as 'down'
dnsdist[29321]: Marking downstream server2
11 matches
Mail list logo