Folks,
This has been a real mystery and haven't been able to find a good
explanation for the behavior. For a simple example I have two views setup and I
want to differentiate access based on queries originating from 127.0.0.1.
In my FIRST ATTEMPT I just negated the IP address, but that didn't
work. The first view never matched. In the SECOND ATTEMPT I simply added
"any" AFTER the negation and that worked?
I read the ARM, can someone explain? Many Thanks!!!!!
FIRST ATTEMPT: Fails - no clients can see external_zones.
view "default-test" {
match-clients { ! 127.0.0.1; }; // thought this would match anyone but
127.0.0.1
zone "." {
type hint;
file "db.cache";
};
zone "0.0.127.in-addr.arpa" {
type master;
file "db.127.0.0.0";
};
include "external_zones.txt";
};
view "default" {
match-clients { any; };
zone "." {
type hint;
file "db.cache";
};
zone "0.0.127.in-addr.arpa" {
type master;
file "db.127.0.0.0";
};
include "internal_zones.txt";
};
SECOND ATTEMPT: Succeeds, only external clients can see external_zones.
view "default-test" {
match-clients { ! 127.0.0.1; any; }; // Why must I add any?
......
----------------
John Murtari - jm5...@att.com
Ciberspring
office: 315-944-0998
cell: 315-430-2702
_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
