20 Říj
2014
20 Říj
'14
9:25
Hi Eric,
On Monday 20 of October 2014 09:01:01 Eric Kom wrote:
NO, I got an existing master server based on BIND9.9 that served the
domain metropolitanbuntu.co.za with slaves and would like to deployed
another master on a different network based on KNOT; so I will like the
listed domain to have 2 masters, in the way that if any record changed
in master based on BIND, KNOT must be notified without manualy changed
the another master if possible.
If you want replication from BIND to Knot DNS, then it is a master-slave
replication. BIND is a master (allows outgoing zone transfers) and Knot DNS is
a slave (pulls zone from master).
But the Knot DNS server can also act as a master and allow outgoing transfers
for other DNS servers on your second network.
This is how a configuration for your Knot DNS server could look like:
remotes {
net0_bind { address 192.168.1.10@53; }
net1_slave1 { address 192.168.2.11@53; }
net1_slave2 { address 192.168.2.12@53; }
}
zones {
metropolitanbuntu.co.za {
# pull zone from BIND on the first network (act as a slave)
xfr-in net0_bind;
notify-in net0_bind;
# provide zone for slaves on the second network (act as a master)
xfr-out net1_slave1, net1_slave2;
notify-out net1_slave1, net1_slave2;
}
}
So yes - the Knot DNS server is a master, but just for the second network. In
relation to the BIND on the first network, it is slave.
If you wanted to sync changes between the BIND and the Knot DNS in both
directions, that would be master-master replication. And we do not support it.
It might work, but you will encounter problems with synchronization if you
perform changes on both servers simultaneously.
Jan
It is possible to do the master to master replication
from BIND to KNOT?
We do not have mechanism for master-master replication. But I think you
are looking for master-slave replication.