BIND appears to be looking at the configuration file from top-down and assigning queries to the first matching view based on match-clients. According to http://www.zytrax.com/books/dns/ch7/view.html that's exactly how it's supposed to work.
In my configuration there may be other views that are applicable to a user in the match-clients configuration and I would like to somehow loop through them. If there's no positive hit (from top-down is fine) it should ideally continue on and check the following views.
Is this somehow possible with BIND? Here's an example. In this below configuration a user from 192.168.1.100 or 192.168.200 would both go only to the first view. Instead I want user 192.168.1.200 to also access the second view.
acl "kids" {
192.168.1.100;
192.168.1.200;
};
view "kids"{
response-policy { zone "kids"; };
match-clients { kids; };
recursion yes;
zone "kids" {
type master;
file "kids.db";
allow-query { none; };
};
};
acl "teens" {
192.168.1.200;
};
view "teens"{
response-policy { zone "teens"; };
match-clients { teens; };
recursion yes;
zone "teens" {
type master;
file "teens.db";
allow-query { none; };
};
};