3 ms·
"Until about a year ago, we instead used a self-hosted PowerDNS on the back-end. PowerDNS was backed by a MySQL (later MariaDB) database. MySQL/MariaDB had been
by Annatar 8y ago
"Until about a year ago, we instead used a self-hosted PowerDNS on the back-end. PowerDNS was backed by a MySQL (later MariaDB) database. MySQL/MariaDB had been chosen for its support for streaming replication."
This is completely unnecessary (to say nothing of how MySQL silently corrupts data): PowerDNS can be configured for regular AXFR's between servers and that works exactly as one would expect, irrespective of what the back-end storage engine is.
The most effective, simplest, robust and therefore cheapest way to run PowerDNS is with the SQLite back-end as the storage engine and AXFR's between master and the slaves configured (PowerDNS BV run it with SQLite themselves); this inter-database replication is nonsense, just asking for trouble due to fragility and complexity. When I see such crazy unnecessarily complex solutions, I often wonder: what the hell went through those people's minds? Aren't they able to reason it out logically? What the hell were they thinking and why the hell were they thinking it??? This solution is so irrational, that it has to be ignorance.
- trobotham 8y agoWe actually chose PowerDNS with MySQL for a chatops style bot which automatically yanks servers in and out of the pool as needed (on splits, when limits are hit, etc), this was for the purpose of load balancing. We then decided to go with Route53 as it is less maintenance and more accurate geo-wise.
- Annatar 8y agoAnd why wouldn't normal AXFR's between servers work in this scenario?
- trobotham 8y agoThe bot would directly update the MySQL database this was also chosen due to the complexity of geodns.
- Annatar 8y agoThis answer makes no sense. Why does an IRC bot have to update the database? What does geolocation have to do with choosing database replication over AXFR? With every answer you raise more questions than you answer.