Hi Thomas,
Most setups I've worked on, didn't move the thousands of domains to LMDB, but
only activated LMDB on demand for domains under attack. The main reason not to
use the LMDB backend for that many domains, is the fact that LMDB doesn't have
any replication mechanisms. Also, the PowerDNS L
Hi Frank,
thanks for noticing the possible speedup by using lmdb Backend instead
of g*sql backends.
Is anyone doing lmdb with millions of Zones? How do you keep them in
sync with the master? Is there also a simple way like mysql replication?
Is it feasible to have a slave servers which check the
Hi,
As Thomas said: your setup looks sane, and if it currently works for you,
there's no need to change anything.
If you do have zones that are getting hit by a random-subdomain-lookup attack,
I would recommend to have a separate NS with a BIND or LMDB backend ready to
serve only those domains
Hi,
as it seems to work for you, why change. Sounds like you are using all
modern technologies which are available.
I run a setup for millions of zones which was designed when dnsdist was
not yet written.
Instead of separating dnsdist, pdns authoritative and mariadb on
separate vms, I run maria
Hi all
I run a reasonably sized PowerDNS setup (high millions of domains across a few
instances). So far the way I have been scaling it is working fine but I would
like to get some addition suggestions in case I missed something. When we need
extra capacity currently its a matter of adding a dn
