Hi Evan, I’m not using the in-view. So, per default this is copied into memory In case of failure of primary the slave can take the lead but in case of a reboot, the slave will not download the copy
If using file option, i should use in-view and then duplicate the zone files. The goal to have two views is only to allow recursion on our internal ip’s. > Le 17 juin 2018 à 21:04, Evan Hunt <e...@isc.org> a écrit : > >> On Sun, Jun 17, 2018 at 05:32:34PM +0000, Nicolas Breuer wrote: >> I have removed the file option in the zone configuration and I can now share >> the same zone on the two views. >> I suspect the zone to be transferred in the memory > > If you're using "in-view", the zone isn't transferred at all. There's a > single copy of the zone in memory, and both views have pointers to it. > You can still use the file option. > > -- > Evan Hunt -- e...@isc.org > Internet Systems Consortium, Inc. _______________________________________________ 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