On 27/06/2017 00:49, James A. Peltier wrote:
Bind does not have a method to do multi-master replication. All updates must be done via an intermediary service (database).
In our case, we've used containers and Consul for providing a highly available DNS service. A container will fire up and race for the master lock. It will dump the contents of the database into its named configurations and assuming it has the lock will assume the IP address of the master. Others just come up as slaves.
If the master lock is not renewed after a given period of time another container can acquire the lock and become master by assuming the IP address of master (VRRP/VRID/KeepAliveD)
Hi James,
Do you have any more info on this setup? I'm in the middle of looking at
changing our DNS service and was thinking of containerising them for the
improved deployment flexibility it offers.
Tris
*************************************************************
This email and any files transmitted with it are confidential
and intended solely for the use of the individual or entity
to whom they are addressed. If you have received this email
in error please notify postmaster@xxxxxxxx
The views expressed within this email are those of the
individual, and not necessarily those of the organisation
*************************************************************
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos
