[Pdns-users] Small site backend recommendations

[Charles Sprickman]

Hello,

We've been using the PDNS recursor for some time now and have been quite
happy with it.  It replaced dnscache and has proven to perform much better.

We're now looking at moving away from tinydns, mainly to get IPv6
support without patching and to get started with DNSSEC.  I don't see us
with more than a few thousand zones anytime soon, and we aren't looking
at anything above 1000 qps (across three servers) anytime soon.

I'm not sure I completely understand the PowerDNS philosophy quite yet,
but it looks like BCP is to run a db server on each name server
(postgres or mysql).  This feels a little too heavyweight for us.  What
might be some interesting options?  Would something like one master with
a "real" db backend (in our case PostgreSQL) and then two slaves running
SQLite work well?  Is there anything "lighter" than SQLite that we could
stick on the slaves?  Is the SQLite backend well-supported?

Any pointers greatly appreciated.  We are committed to a database-backed
DNS server (we currently have a script that dumps db data to a tinydns
data file), and there do not seem to be that many actively-developed
options out there...

Thanks,

Charles