On Jan 7 2013, Phil Mayers wrote:
[...]
I've never tried it but there's a "journal" option on the zone; maybe
this takes paths, like so:
zone "foo" {
type master;
# zone lives outside working dir
file "/etc/zones/foo";
# ...but journal lives inside it
journal "data/journals/foo";
};
Note: I've never tested this; it is a wild guess.
We have been using it for years - it works fine. We have e.g.
zone "cam.ac.uk" {
type master;
file "master/cam.ac.uk";
journal "master-jnl/cam.ac.uk";
...
}
zone "111.131.in-addr.arpa" {
type master;
file "master/111.131.in-addr.arpa";
journal "master-jnl/111.131.in-addr.arpa";
...
}
...
zone "cl.cam.ac.uk" {
type slave;
file "slave/cl.cam.ac.uk";
journal "slave-jnl/cl.cam.ac.uk";
...
};
zone "232.128.in-addr.arpa" {
type slave;
file "slave/232.128.in-addr.arpa";
journal "slave-jnl/232.128.in-addr.arpa";
...
};
...
One slight niggling disadvantage is that you can't tell
named-checkzone / named-compilezone with the -j option where
to find the journal is it isn't in the default location.
--
Chris Thompson
Email: c...@cam.ac.uk
_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
