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

bind. If you need more performance switch the Backend to NSD or Knot. regards Klaus > -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] dn

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

rst test your Backend performance to know how much qps a single backend can handle. I guess 500k qps might be difficult to achieve with bind. If you need more performance switch the Backend to NSD or Knot. regards Klaus > -Ursprüngliche Nachricht- > Von: dnsdist Im Auftrag von >

Re: [dnsdist] Latency and backend down issue

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 waiting for the health check response from backend 19

[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 waiting for the health check response from backend 192

[dnsdist] Latency and backend down issue

Hi, We are seeing backend down issue and latency increase as well. Load traffic tested with 50K as well as 30K. same behavior. Implemented different configuration to diagnose this issue. Please help. Regards, Rais ___ dnsdist mailing list dnsdist@mail

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

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