In article ,
p...@mail.nsbeta.info wrote:
> In fact I want to the clients that match view_b to fall into the default
> view, say it's view_c.
There is no fall-through in views. The search stops when it finds the
first view that matches. Each view is like a totally separate server
(which i
In message <20110121030937.da19e2c...@mail.nsbeta.info>, p...@mail.nsbeta.info w
rites:
> Mark Andrews writes:
>
> >
> > In message <20110121024745.bcd2e2c...@mail.nsbeta.info>, p...@mail.nsbeta.in
> fo w
> > rites:
> >>
> >> Hello,
> >>
> >> My named.conf looks as:
> >> --
Mark Andrews writes:
In message <20110121030937.da19e2c...@mail.nsbeta.info>, p...@mail.nsbeta.info w
rites:
In fact I want to the clients that match view_b to fall into the default
view, say it's view_c.
You need view_b to have a copy of view_c's zone. See the archives for
how to do th
Mark Andrews writes:
In message <20110121024745.bcd2e2c...@mail.nsbeta.info>, p...@mail.nsbeta.info w
rites:
Hello,
My named.conf looks as:
--
view "view_a" {
match-clients {
IP_ADDR_A;
};
zone "test.com" {
type master;
In message <20110121024745.bcd2e2c...@mail.nsbeta.info>, p...@mail.nsbeta.info w
rites:
>
> Hello,
>
> My named.conf looks as:
> --
> view "view_a" {
> match-clients {
> IP_ADDR_A;
> };
> zone "test.com" {
> type master;
> fil
Hello,
My named.conf looks as:
--
view "view_a" {
match-clients {
IP_ADDR_A;
};
zone "test.com" {
type master;
file "test.com.a.db";
};
};
view "view_b" {
match-clients {
IP_ADDR_B;
};
# doesn't have test.com z
6 matches
Mail list logo
