We are happy to announce that Vesta is back under active development as of 25 February 2024. We are working on v1 candidate and expect to engage more with the community over the coming months. We are committed to open source, and we encourage contributors to help us build the future of Vesta.
Discussion about DNS Cluster
Discussion about DNS Cluster
As I have figured it out, DNS Cluster is setting up a Master – Master – Master scenario. All of the domain zones in cluster members are of type Master and there exist no slave zone. This configuration has its problems as you can see here.
How about this approach?
How about this approach?
- Ability to select between DNS Cluster (as it is now) or (a new setup) Master-Slave
- In Master-Slave setup, when we add a new slave server, the bind conf file will be updated to allow zone transfers and enable notify to this server
- When a new domain is added on the Master server, the script will handle the addition of this zone to the slave(s) server(s) and schedule regular zone transfer requests from the Master
- When a domain is edited on the Master, it will automatically initiate a zone transfer
- On the master server there will be a cron job (like the script v-update-sys-queue dns-cluster) that checks if the Master Zones exist on the Slaves, in case someone manually deletes the zone from the slave. If it doesn't find it, it will create it again.