On Sun, Jun 17, 2018 at 07:10:11PM +0000, Nicolas Breuer wrote:
> 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
I think I'd have to see your config to understand. But if you
had it like this:
view a {
zone foo.com {
type slave;
masters { ... };
file "filename";
...
};
};
view b {
zone foo.com {
in-view a;
};
};
... then you'd have foo.com accessible within both views, and it will
be saved only once, in "filename".
> The goal to have two views is only to allow recursion on our internal ip’s.
If you don't have any zones that differ between your internal
and external views, then views are unnecessary. Just use
"allow-recursion { localnets; };" and external queries won't be
allowed to do recursion.
--
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
