How to handle zones that need to be the same in all views?
barmar at alum.mit.edu
Tue Jun 12 03:41:33 UTC 2012
In article <mailman.1002.1339459440.63724.bind-users at lists.isc.org>,
Max Bowsher <_ at maxb.eu> wrote:
> That won't help me for slave zones:
> * the zones get needlessly re-transferred once for each view
Unless they're huge, so what?
> * the files on disk will be repeatedly overwritten as bind tries to save
> the zone data separately for each zone, to the same filename
Again, so what?
> * bind will only act on a notify for the view that receives it, leaving
> all the other views serving stale data for the zone
So the masters don't have all the different views? Maybe it would be
easier to use periodic file transfers of the zone files. Then configure
your server as a master rather than a slave. You could then point to
the same zone files in all the views as well, so you would only have to
transfer the zone once.
> On 11/06/12 22:17, andrew kagan wrote:
> > Max: are you familiar with BIND's "include" syntax? Just put all the
> > zones in an include file, then include in each view?
> > http://www.zytrax.com/books/dns/ch7/include.html
> > http://www.zytrax.com/books/dns/ch8/include.html
> > On 6/11/2012 2:09 PM, Max Bowsher wrote:
> >> 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.
More information about the bind-users