How to handle zones that need to be the same in all views?
p.mayers at imperial.ac.uk
Tue Jun 12 08:09:35 UTC 2012
On 06/12/2012 01:03 AM, Max Bowsher wrote:
> That won't help me for slave zones:
> * the zones get needlessly re-transferred once for each view
If you actually want a copy of each zone in each view, you can't avoid this.
> * the files on disk will be repeatedly overwritten as bind tries to save
> the zone data separately for each zone, to the same filename
This does rule out includes; they only work for static zones.
> * bind will only act on a notify for the view that receives it, leaving
> all the other views serving stale data for the zone
Again, this is hard to avoid unless you burn a lot of IPs.
Have you considered a single view containing all the common zones, then
a view per "different" zone that forwards to 127.0.0.1? Provided you
arrange your "match-clients" correctly this should work.
You may wish to investigate the attach-cache option, so that all the
forwarding views can share cache results.
Bear in mind that the forwarding views will not see changes in the
common view immediately, but will have to wait for TTL expiry. There's
not much you can do about this.
Basically, there's no trick to do what you want; bind isn't designed to
share non-static zone data between zones.
More information about the bind-users