How to handle zones that need to be the same in all views?

Max Bowsher _ at
Mon Jun 11 21:09:12 UTC 2012

I've inherited some responsibility for existing DNS system that makes
extensive use of BIND's view feature (there are 10 views; external,
internal-site1, internal-site2, ...etc...).

I'm experiencing a problem in that there's really only one zone that
differs between views, and now I'm facing the difficulty of wanting to
have these multi-viewed nameservers act as slaves for some additional
zones; with the slaved data being identically visible to all views.

In a perfect world, BIND would let me tell it that some zones were
global to all views, but this feature doesn't seem to exist.

Does anyone have any suggestions for how to structure a setup like this?

About the only possibility I can come up with is to run two different
sets of nameservers, one for the zones that need to be different across
views, and one for the zones that need to be global.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: OpenPGP digital signature
URL: <>

More information about the bind-users mailing list