Hi Atha, Just though I would add that this is exactly how we do things where I work, but with an additional layer that may or may not be necessary for you.
We have our slaves behind load balancers (Nortel Alteon's in our case) that can do UDP session balancing so that there is literally no down time ever, not even the odd timeout if a slave dies since the load balancer just fails the server and the load is moved onto the remaining slaves. Very handy if you have any applications that are very sensitive with regards to the speed of DNS responses, and especially if you have some load balancers that do the job in your network already! Other than that I can heartily recommend a deployment along these lines. Cheers, Josh ________________________________________ Atha, Let me share with you what we did at the company I used to work for (and this is an identical configuration to what I have setup for myself). We don't have master and slave PDNS servers. We have "workers" of sorts. Our master and slaves are the MySQL backends. We have a master MySQL server which is the server that we perform all writes against. It serves as the master backend, and no PDNS installations connect to it directly. In fact, PDNS isn't even installed on the server that hosts the master backend. Then, on each physical (or virtual) DNS server, we have MySQL server and PDNS installed. The MySQL server, which is a slave backend, replicates off of the master backend. Then, PDNS connects to the local MySQL server for its backend. <snip> Nick On Nov 10, 2010, at 8:29 AM, Atha Kouroussis wrote: Hi all, we are looking to migrate from bind to PowerDNS with MySQL backend. Our initial tests have gone really well and we are now looking into finalizing the architecture for the final deployment and migration. In that respect we have a couple of doubts. Since we are going to be using the MySQL backend, and we are going to have multiple PowerDNS servers deployed, is it possible to have several instances of pdns share the same backend? How does that affect slave updates in case a master has more than one slave configured and both slaves use the same backend? If its not possible to use the same backend, we are thinking of using MySQL replication, master-slave, and have only one pdns instance listed as slave. What we don't like about this setup is the lack of redundancy since in order to have more than one slave listed we would have to use master-master replication, which we are trying to avoid. What are your thoughts on this? Are there any best practices/recommendations for large deployments? Thanks in advance for all your help. Cheers, Atha _______________________________________________ Pdns-users mailing list [email protected]<mailto:[email protected]> http://mailman.powerdns.com/mailman/listinfo/pdns-users _______________________________________________ Pdns-users mailing list [email protected] http://mailman.powerdns.com/mailman/listinfo/pdns-users
