In message <49800cfd.nihabiqjcalhfl+u%[email protected]>, Andy Kosela writ
es:
> "Reinis Rozitis" <[email protected]> wrote:
>
> > > I've been using an include file for zones common between multiple
> > > views, might help in your case too.
> >
> > Thanks somehow didnt think about this way. Pretty much takes to
> > acceptable solution :)
>
> Yes, "include" statement is the best option especially if you have a lot
> of zones. That aproach also works great if you need to provide
> recursion for some of your clients *and* serve authoritative records for
> the rest of the world. By creating multiple views you can also easily
> disable answering queries for "." to unknown clients.
>
> view "internal" {
> match-clients { "LAN"; };
> recursion yes;
> include "zones";
> };
>
> view "external" {
> match-clients { any; };
> recursion no;
> additional-from-cache no;
> include "zones";
> };
Or just run a currently supported version and specify
options {
allow-recursion { LAN; };
};
include "zones";
and achieve the same thing for half the memory footprint and
not have to worry about different views clobbering the same
masterfiles.
Mark
> --Andy
> _______________________________________________
> bind-users mailing list
> [email protected]
> https://lists.isc.org/mailman/listinfo/bind-users
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: [email protected]
_______________________________________________
bind-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/bind-users
