Re: [dnsdist] dnsdist[29321]: Marking downstream IP:53 as 'down'

2022-03-31 Thread Rais Ahmed via dnsdist
ver 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.powerdns.com Subject: AW: [dnsdist] dnsdist[29321]: Marking downstream IP:53 as 'down' Have you te

Re: [dnsdist] dnsdist[29321]: Marking downstream IP:53 as 'down'

2022-03-24 Thread Klaus Darilion via dnsdist
@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 interface

Re: [dnsdist] dnsdist[29321]: Marking downstream IP:53 as 'down'

2022-03-24 Thread Rasto Rickardt via dnsdist
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' Have

Re: [dnsdist] dnsdist[29321]: Marking downstream IP:53 as 'down'

2022-03-24 Thread Rais Ahmed via dnsdist
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? First test y

Re: [dnsdist] dnsdist[29321]: Marking downstream IP:53 as 'down'

2022-03-24 Thread Klaus Darilion via dnsdist
> -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 for reply.

Re: [dnsdist] dnsdist[29321]: Marking downstream IP:53 as 'down'

2022-03-23 Thread Willis, Michael via dnsdist
.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=DNSClass.IN, checkName="www

Re: [dnsdist] dnsdist[29321]: Marking downstream IP:53 as 'down'

2022-03-23 Thread Willis, Michael via dnsdist
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 albeit on a smaller sc

Re: [dnsdist] dnsdist[29321]: Marking downstream IP:53 as 'down'

2022-03-23 Thread Willis, Michael via dnsdist
] 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:53 Timeout while

[dnsdist] dnsdist[29321]: Marking downstream IP:53 as 'down'

2022-03-23 Thread Rais Ahmed via dnsdist
t..." 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) -- Message: 1 Date: Tue, 22 Mar 2022 23:00:25 +0

Re: [dnsdist] dnsdist[29321]: Marking downstream IP:53 as 'down'

2022-03-23 Thread Remi Gacogne via dnsdist
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' > > dn

[dnsdist] dnsdist[29321]: Marking downstream IP:53 as 'down'

2022-03-22 Thread Rais Ahmed via dnsdist
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