How to define views that differ only minimally?

[Kevin Darcy]

Depending on what you are trying to accomplish, and subject to a number 
of caveats, sometimes sortlists are a better option than views. E.g. 
define foo.zone.example to resolve to 10.8.0.1 *and* 85.214.68.41 and 
sortlist the answer accordingly. It looks like you're trying to do a 
NAT/split-name thing with this, however, so sortlisting would probably 
not be a good solution for you (don't want to leak 10.*.*.* addresses to 
the Internet).

- Kevin

Marc Haber wrote:
> Hi,
>
> Let us assume that S is a bind 9.3.4 server on Linux, authoritative
> for a number N of zones (let N be around a couple of thousand). Now,
> we need a small number of zones (around two or three) in different
> views, like resolve foo.zone.example to 10.8.0.1 if the client is in
> the 10.8.0.0/24 network, and to 85.214.68.41 if the client is
> somewhere else.
>
> >From what I understand from reading the ARM, I now need to generate
> two views that both include zone statements for all thousands of
> zones, with only the zone statements of the zones that need to differ
> differently. This also means that if a second customer wants a similar
> setup, I need to have the thousands of zones a third time. And I
> assume that each zone file gets actually loaded multiple times, right?
>
> Isn't it possible to have a view B defined as "as view A with the
> following exceptions"?
>
> Any hints will be appreciated.
>
> Greetings
> Marc
>
>