TR: Slave Zones for Bind 9.11

[Nicolas Breuer]

I have setup like this :



view "DNS" {



allow-recursion { acl-allow; };





zone "." {

        type hint;

        file "named.ca";

};



include "/etc/named/zones";



};



Seems working 😊





-----Message d'origine-----
De : Evan Hunt [mailto:each at isc.org]
Envoyé : dimanche 17 juin 2018 22:59
À : Nicolas Breuer <Nicolas.Breuer at belcenter.biz>
Cc : bind-users at lists.isc.org
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 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 -- each at isc.org<mailto:each at isc.org>

Internet Systems Consortium, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20180618/663b3cfa/attachment.html>