[Pdns-users] Small site backend recommendations

ktm at rice.edu ktm at rice.edu
Thu May 12 12:27:29 UTC 2011

On Thu, May 12, 2011 at 03:37:24AM -0400, Charles Sprickman wrote:
> 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

Hi Charles,

The advantages to having a db for each server is redundancy. A single
server can easily serve 10X you expected load on a single box. I addition
using db replication to move the updates around provides for a much more
real-time process across all of your systems.


More information about the Pdns-users mailing list