Hi Giovanni, Knot DNS doesn't support master-to-master synchronization.
Why don't you want master-slave topology? You can have one hidden master, more public masters, which would be slaves of the hidden master, and possible slave servers with more masters. It's quite common strategy and easy to realize. I think that a disadvantage of multi master is rare implementation in DNS servers. Also it's out-of-scope of DNS so there are not standards how to do that. But a very simple solution could be distribution of your zone file (over ssh) among the master servers and reload them synchronously :-) What type of zone changes do you plan to perform? Simple zone file updates, dynamic DNS updates, or/with automatic DNSSEC signing? Regards, Daniel On 03/03/2017 11:47 AM, Giovanni Civardi wrote:
Hi, i’m evaluating some DNS solution for our multi-site distributed environment. I do not want a master-slave scenario, but would like to implement some multi-master. do you think is achievable with KNOT? have you ever implemented some master-to-master synchronisation? what could be the benefits having a multi-master scenario against the classic master-slave scenario? thanks! *Giovanni Civardi* System Engineer *MainStreaming* Phone+39 02 868969.69 Webhttp://www.mainstreaming.tv _______________________________________________ knot-dns-users mailing list [email protected] https://lists.nic.cz/cgi-bin/mailman/listinfo/knot-dns-users
_______________________________________________ knot-dns-users mailing list [email protected] https://lists.nic.cz/cgi-bin/mailman/listinfo/knot-dns-users
