TR: Slave Zones for Bind 9.11

Nicolas Breuer Nicolas.Breuer at
Mon Jun 18 07:30:27 UTC 2018

1000x thanks Evan for your advises.

I will try  to modify the configuration with the allow-recursion options.

-----Message d'origine-----
De : Evan Hunt [mailto:each at] 
Envoyé : dimanche 17 juin 2018 22:59
À : Nicolas Breuer <Nicolas.Breuer at>
Cc : bind-users at
Objet : Re: TR: Slave Zones for Bind 9.11

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 {
              type slave;
              masters { ... };
              file "filename";

        view b {
           zone {
               in-view a;

... then you'd have 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 -- each at
Internet Systems Consortium, Inc.

More information about the bind-users mailing list