Hi.
I've been trying to find examples on how to use TSIG to replicate several
differents views to a slave server, but I could only find with two views,
and I just couldn't figure out how to adapt that example to 3 or more views.
Could you send me example on how to accomplish that?
Thanks!
In article mailman.1019.1339549231.63724.bind-us...@lists.isc.org,
Mark Andrews ma...@isc.org wrote:
This really isn't that hard. Just use tsig and transfer the zone
between views on the slave machine. Just ensure that you transfer
from the view that is getting the notify messages from the
Mark Andrews ma...@isc.org wrote:
This really isn't that hard. Just use tsig and transfer the zone
between views on the slave machine. Just ensure that you transfer
from the view that is getting the notify messages from the master.
Thanks Mark, that's definitely a workable (if not very
In message 4fd8b4e1.3070...@maxb.eu, Max Bowsher writes:
Mark Andrews ma...@isc.org wrote:
This really isn't that hard. Just use tsig and transfer the zone
between views on the slave machine. Just ensure that you transfer
from the view that is getting the notify messages from the
On 06/12/2012 01:03 AM, Max Bowsher wrote:
That won't help me for slave zones:
* the zones get needlessly re-transferred once for each view
If you actually want a copy of each zone in each view, you can't avoid this.
* the files on disk will be repeatedly overwritten as bind tries to save
This really isn't that hard. Just use tsig and transfer the zone
between views on the slave machine. Just ensure that you transfer
from the view that is getting the notify messages from the master.
You will want BIND 9.9.x or later.
Mark
key view1 {
};
key view16 {
I've inherited some responsibility for existing DNS system that makes
extensive use of BIND's view feature (there are 10 views; external,
internal-site1, internal-site2, ...etc...).
I'm experiencing a problem in that there's really only one zone that
differs between views, and now I'm facing the
That won't help me for slave zones:
* the zones get needlessly re-transferred once for each view
* the files on disk will be repeatedly overwritten as bind tries to save
the zone data separately for each zone, to the same filename
* bind will only act on a notify for the view that receives it,
In article mailman.1002.1339459440.63724.bind-us...@lists.isc.org,
Max Bowsher _...@maxb.eu wrote:
That won't help me for slave zones:
* the zones get needlessly re-transferred once for each view
Unless they're huge, so what?
* the files on disk will be repeatedly overwritten as bind
9 matches
Mail list logo
