about organization of dns views

[Barry Finkel]

"Fabiano Silos Reis" <fsilos at ig.com> wrote:

>I would like to configure dns view as clean as possible, but i´m getting some problems with this task. At named.conf I have:
>
> 
>
>. . . 
>
> 
>
>view "internal" {
>
>        match-clients { "acl-internal"; };
>
>        include "zones-internal.inc";
>
>};
>
> 
>
>view "internal" {
>
>        match-clients { any; }; // everyone who is not "internal"
>
>        include "zones-external.inc";
>
>};
>
> 
>
> 
>
>At zones-internal.inc I have:
>
> 
>
>zone "domain.com.br" {
>
>        type master;
>
>        file "virtual_domains/domain.com.br-internal";
>
>};
>
> 
>
>At zones-external.inc I have:
>
> 
>
>zone "domain.com.br" {
>
>        type master;
>
>        file "virtual_domains/domain.com.br";
>
>};
>
> 
>
>zone "domain2.com.br" {
>
>        type master;
>
>        file "virtual_domains/domain2.com.br";
>
>};
>
> 
>
> 
>
>The question I have here is: Why domain2.com.br is not resolved when I
>ask my dns from an IP address that is defined in acl-internal? Is there
>a way to do that without defining this zone at "internal" view? If yes,
>I think it will more easy to deal with my configuration zone files
>because I have a lot of zones and I wouldnt like to repeat these zones
>inside each view I have...

I think the problem is this - any zone that is common to both views
must be included in both views.  In my BIND configuration I have
a separate file named.conf.non-views that contains the zone definitions
for zones that are in both views.  I just $INCLUDE that file in each
view.
----------------------------------------------------------------------
Barry S. Finkel
Computing and Information Systems Division
Argonne National Laboratory          Phone:    +1 (630) 252-7277
9700 South Cass Avenue               Facsimile:+1 (630) 252-4601
Building 222, Room D209              Internet: BSFinkel at anl.gov
Argonne, IL   60439-4828             IBMMAIL:  I1004994