Rehashing split views et al in bind 9.1

[Glenn Bell]

I included my whole view in a single file as follows.

// Bind 9.x named.conf
options {
    directory "/etc/named";
    forwarders { <IP_ADDR>; };
    dump-file "/var/tmp/name_dump.db";
    statistics-file "/var/tmp/named.stats";
    pid-file "named.pid";
    auth-nxdomain no;
    provide-ixfr yes;
    transfer-format one-answer;
    transfers-in 30;
    transfers-out 30;
    transfers-per-ns 5;
};

// Server Specific Information is stored in a seperate file
include "servers.inc";

// The actual views are managed in seperate files
include "external.inc";
include "internal.inc";

<EOF>

// external.inc
view "external" {
    match-clients {
        <IP_ADDR>;
    };

    zone "." {
        type hint;
        file "named.root";
    };

    zone "mitre.org" {
        type master;
        file "external/mitre.org";
        also-notify {
            <IP_ADDR>;
        };
    };

    zone "83.129.in-addr.arpa" {
        type master;
        file "external/129.83.rev";
        also-notify {
            <IP_ADDR>;
        };
    };
};

<EOF>

I am running this configuration on a Sun E250 running Solaris 2.6.  It
has been running without incident since the upgrade.

Hope this helps.

-Glenn

Cott Lang wrote:
> 
> So I guess the conclusion of this thread is that include doesn't work in
> views...
> 
> Any possibility it'll ever work in views?
> 
> ----- Original Message -----
> From: "Mark Chesterfield" <mark at ennu.com.au>
> Newsgroups: comp.protocols.dns.bind
> To: <comp-protocols-dns-bind at moderators.isc.org>
> Sent: Sunday, February 11, 2001 5:22 PM
> Subject: Re: Rehashing split views et al in bind 9.1
> 
> > I too am having this problem. I tried quoting the filename, tried
> upgrading
> > to 9.1.1.rc1 but to no avail.
> >
> > Any chance of posting a sanitised config set that works ?
> >
> > "Glenn Bell" <glennb at mitre.org> wrote in message
> > news:961p04$m8p at pub3.rc.vix.com...
> > > I had the same problem.  Quote the file names.
> > >
> > > include "externals.inc"
> > >
> > > This solved the problem for me.
> > >
> > > -Glenn
> > >
> > > Cott Lang wrote:
> > > >
> > > > >>of external domains in both the internal and external view. However,
> > > > include
> > > > >>doesn't appear to work within a view?!  This seems rather
> unbelievable
> > to
> > > > >>me - am I doing something wrong?
> > > > >
> > > > >Not my experience. $include (not #include, of course), seems to work
> > fine
> > > > >here. The zone files referenced in my named.conf contain only one
> > > > >$include line for the external view, and two $include lines for the
> > > > >internal view. All the rest is in the included files.
> > > >
> > > > I'm talking about using include (no, not #include :)) in the actual
> > > > named.conf file, not in the zone files... I see the advantage in using
> > > > $include in the zone files, but that doesn't seem to help my situation
> > of
> > > > having hundreds of zones, most of which need to be fed to internal &
> > > > external users - unless there's a conditional zone include I could use
> > only
> > > > on my two domains that I need different.  I assume one can't define
> the
> > same
> > > > zone twice with different allow-query strings... :)
> > > >
> > > > i.e.
> > > >
> > > > view "internal" {
> > > >   zone "myinternalzone" {
> > > >     blah;
> > > >   }
> > > >
> > > >   include externals.inc;    // includes my 100+ zones
> > > > }
> > > >
> > > > view "external" {
> > > >   match-clients { any; };
> > > >   include externals.inc;    // includes my 100+ zones
> > > > }
> > > >
> > > > I get a parsing error on any include lines inside a zone. If I moved
> it
> > > > outside a zone, it works fine.
> > > >
> > > > I should add the problem with using forwarding is that internal
> clients
> > > > (including DNS servers) can't go outside the firewall using NAT and
> make
> > a
> > > > connection to a public IP on the same firewall....
> >
> >
> >
> >
> >