[Pdns-users] Small site backend recommendations

Chris Russell Chris.Russell at knowledgeit.co.uk
Thu May 12 08:23:59 UTC 2011

Hi Charles,

 We're in a similar position right now (a current scripted solution, active development in other servers, etc) and I've came up against some of the same issues. Decided against the Bind DLZ system, despite meeting some of the ISC staffers and am sticking with PowerDNS.

 I can't comment on the backend options but a hidden master is preferable to hide some of the keyring information on DNS-SEC. That said, right now I`m torn between using a similar solution to yourself in a database driven hidden master and DNS slave backends, or using MySQL replication to do a similar role.

 One thing I did find, not sure if it's still current is this - http://community.plus.net/blog/2008/03/13/about-the-plusnet-authoritative-dns-system/

 There seems to be loads of information of creating a very basic setup, but little in terms of who's really using PowerDNS and how. That said though, the list is very helpful :)



-----Original Message-----
From: pdns-users-bounces at mailman.powerdns.com [mailto:pdns-users-bounces at mailman.powerdns.com] On Behalf Of Charles Sprickman
Sent: 12 May 2011 08:37
To: pdns-users at mailman.powerdns.com
Subject: [Pdns-users] Small site backend recommendations


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...


Pdns-users mailing list
Pdns-users at mailman.powerdns.com

Knowledge I.T.
'Unifying Business Technology'

Knowledge Limited, Company Registration: 1554385
Registered Office: New Century House, Crowther Road, Washington, Tyne & Wear. NE38 0AQ
Leeds Office: Viscount Court, Leeds Road, Rothwell, Leeds. LS26 0GR

Tel: 0845 142 0020. Fax: 0845 142 0021

E-Mail Disclaimer: This e-mail message is intended to be received only by persons entitled to receive the confidential information it may contain. E-mail messages to clients of Knowledge IT may contain information that is confidential and legally privileged. Please do not read, copy, forward, or store this message unless you are an intended recipient of it. If you have received this message in error, please forward it to the sender and delete it completely from your computer system.

Please consider the environment before printing this email.

More information about the Pdns-users mailing list