Can two views be layered?

Novosielski, Ryan novosirj at umdnj.edu
Fri Apr 5 20:24:24 UTC 2013


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 03/15/2013 07:11 PM, Joseph S D Yao wrote:
> On Fri, Mar 15, 2013 at 06:56:57PM -0400, Novosielski, Ryan wrote:
>> Hi all. Running BIND 9.6 I believe it is. Not important what
>> version as if there is a version that can do this and I'm not
>> running it, I can go there.
>> 
>> Is it possible to have a view that is in essence a list of
>> exceptions to the main zone? eg. the example.com domain exists,
>> so does www.example.com, but for a small subset of machines I
>> need it to resolve to a different address -- every other address
>> should come from the main zone.
>> 
> 
> 
> It is not possible to have views layered as you describe.  However,
> try this:
> 
> file zonename.shared with all shared records. file
> zone.zonename.for-the-many with the records for the many. $INCLUDE
> "zonename.shared" File zone.zonename.for-the-few with the records
> for the few. $INCLUDE "zonename.shared"

... SNIP...

One followup question to this: are there any limits to how the SOA
section is handled in this case? Can the SOA record be in the
$INCLUDE'd file, or does it have to be in the defined zone files
(which then would mean maintaining I guess two serial numbers)? I was
originally thinking that in that case, whenever changes are made to
the zonename.shared file, all that was really needed to be updated was
the "for-the-many" zone but I believe then the "for-the-few" machines
would begin to see an increasingly out of date version of the shared file.

- -- 
- ---- _  _ _  _ ___  _  _  _
|Y#| |  | |\/| |  \ |\ |  | |Ryan Novosielski - Sr. Systems Programmer
|$&| |__| |  | |__/ | \| _| |novosirj at umdnj.edu - 973/972.0922 (2-0922)
\__/ Univ. of Med. and Dent.|IST/EI-Academic Svcs. - ADMC 450, Newark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iEYEARECAAYFAlFfMu8ACgkQmb+gadEcsb54vACgimqYO1V5TdzpGn7o2WbR224t
QFkAoL+up2JbCAd4LccsMo7d8sRJEOFE
=XqTS
-----END PGP SIGNATURE-----



More information about the bind-users mailing list