view problem

Mark Andrews marka at
Tue Oct 18 22:50:14 UTC 2016

In message <alpine.DEB.2.20.1610181109390.8821 at>, Jay Ford writes:
> On Tue, 18 Oct 2016, Barry Margolin wrote:
> > If there are zones that both sets of clients should see, you have to
> > duplicate them in both views. Overlapping views don't do this
> > automatically.
> Right.  "in-view" can be useful for this, as long as you only need to refer 
> to previously defined views (i.e., it unfortunatley doesn't allow forward 
> references).

So put the zone in the first view.  Updates, notifies and queries
are delivered to the zone from all views the zone is in.  Acls are
all configurable on the zone level if you don't like the inherited
acls from the first view.

To get any order we need to configure all views without the in-view
zones then go back and configure all the in-view zones.

We then would need to go and configure all the automatic empty zones
as they need to be aware of bottom of zone cuts.

It's do able but it isn't high on the priority list.


> ________________________________________________________________________
> Jay Ford, Network Engineering Group, Information Technology Services
> University of Iowa, Iowa City, IA 52242
> email: jay-ford at, phone: 319-335-5555
> _______________________________________________
> Please visit to unsubscribe from this list
> bind-users mailing list
> bind-users at
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka at

More information about the bind-users mailing list