On Fri, Jul 16, 2021 at 12:21 PM Peter van Dijk via Pdns-users <
pdns-users@mailman.powerdns.com> wrote:
> On Fri, 2021-07-16 at 12:08 +0200, Thomas Mieslinger via Pdns-users
> wrote:
> > Suggestions from older threads (Klaus Darrilon):
> > - Put that zone in a more efficent Backend (he suggested
On Fri, 2021-07-16 at 12:08 +0200, Thomas Mieslinger via Pdns-users
wrote:
> Suggestions from older threads (Klaus Darrilon):
> - Put that zone in a more efficent Backend (he suggested lmdb)
Good idea.
> - Put that zone in a more efficent Software (he suggested nsd) and use
> dnsdist to route the
Suggestions from older threads (Klaus Darrilon):
- Put that zone in a more efficent Backend (he suggested lmdb)
- Put that zone in a more efficent Software (he suggested nsd) and use
dnsdist to route the traffic to the alternate Software
Very old suggestion:
- Use a firewall uint32 match to loc
Hello,
We have received a DDoS attack on our powerdns infrastructure.
The DNS requests were all non-existing records in 1 single zone.
Eg:
ghz2.mydomain.com
cdzx.mydomain.ocom
hh3r.mydomain.com
The result was that the SQL backend was overloaded with these queries and
caused some of our se
