Hi all, I am just curious if anyone on the list has any comments on this. I don't feel like I am being overly paranoid here - database failure are few and far between but if the DB goes away not serving DNS records is a bad thing. What is the general thoughts on this?
Thanks, Max On 4/12/07, Max Clark <[EMAIL PROTECTED]> wrote:
Hi all, We are currently running pdns with a mysql backend and relying on mysql master->slave replication to keep our records up to date. While we want to keep the mysql backend for the master due to ease of use and the ability to integrate our own custome front end management to it, there has been a discussion lately about what to do with our public authorative servers. Relying on the mysql backend for replication adds a layer of complexity to the environment that we are not exactly thrilled with. If the replication stops, or the mysql slave service dies, or simply gets overwhelmed AUTH DNS goes down. This for obvious reasons is not desired. I am looking for advice/recommendations on this environment where we can have authorative slaves that are not dependant on mysql - but still benefit as much as possible from the automatic provisioning and pruning of the zones from the master. Thanks in advance, Max -- Max Clark http://www.clarksys.com
_______________________________________________ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users