Support for split horizon should be added
Support for split horizon should be added
We should be able to add views and assign zones to them.
(from redmine: issue id 4504, created on 2016-02-11, closed on 2016-03-14)
- Relations:
- copied_to #4506
- Changesets:
- Revision f2688d8d by Côme Chilliet on 2016-02-11T10:57:02.000Z:
Fixes #4504 Added preliminary split horizon DNS view support- Revision c5c12209 by Côme Chilliet on 2016-02-11T15:32:20.000Z:
Fixes #4504 Added preliminary split horizon DNS view support- Revision bad51f93 by Côme Chilliet on 2016-03-10T11:22:59.000Z:
Fixes #4504 Fixed DNS views schema- Revision d49d56ad by Côme Chilliet on 2016-03-10T11:23:34.000Z:
Fixes #4504 Fixed DNS views schema- Revision e1915931 by Côme Chilliet on 2016-03-14T09:58:09.000Z:
Fixes #4504 Added separated DNS Acl objects- Revision 42b9421f by Côme Chilliet on 2016-03-14T10:00:54.000Z:
Fixes #4504 Added separated DNS Acl objects- Revision f8d5a5f2 by Benoit MORTIER on 2016-03-14T11:19:52.000Z:
Fixes #4504 Added separated DNS Acl objects
corrected sentences wording
Signed-off-by: Mortier Benoit <benoit.mortier@opensides.be>- Revision 5f495b68 by Benoit MORTIER on 2016-03-14T11:54:43.000Z:
Fixes #4504 Added separated DNS Acl objects
corrected sentences wording
Signed-off-by: Mortier Benoit <benoit.mortier@opensides.be>- Custom Fields:
- Bug in version: 1.0.9.3
Activity
hello,
we should have the choice of using
match-clients match-destination match-recursive only
match-clients
match-clients { address_match_element; ... }; match-clients { 10.2.3.0/8;172.16.30.0/16;!192.168.0.0/16; };
the above could be re-written as
match-clients { 10/8;172.16/16;!192.168/16; };
(More info on IP Prefix notation)
A view clause matches when either or both of its match-clients and match-destinations statements match and when the match-recursive-only condition is met. If either or both of match-clients and match-destinations are missing they default to any (all hosts match). The match-clients statement defines the address_match_list for the source IP address of the incoming messages. Any IP which matches will use the defined view clause. This statement may only be used in a view clause. match-destinations
match-destinations { address_match_element; ... }; match-destinations { 192.168.0.3; };
A view clause matches when either or both of its match-clients and match-destinations statements match and when the match-recursive-only condition is met. If either or both of match-clients and match-destinations are missing they default to any (all hosts match). The match-destination statement defines the address_match_list for the destination IP address of the incoming messages. Any IP which matches will use the defined view clause. This statement may only be used in a view clause. match-recursive-only
match-recursive-only (yes | no); match-recursive-only yes;
A view clause matches when either or both of its match-clients and match-destinations statements match and when the match-recursive-only condition is met. If either or both of match-clients and match-destinations are missing they default to any (all hosts match). The match-recursive-only can be used in conjunction with match-clients and match-destinations or on its own if that is sufficient differentiation. The default is no. This statement may only be used in a view clause.
(from redmine: written on 2016-02-18)
Hello,
schema is not working
SASL/EXTERNAL authentication started SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth SASL SSF: 0 executing 'ldapmodify -Y EXTERNAL -H ldapi:/// -f /etc/ldap/schema/fusiondirectory/dns-fd_update.ldif' SASL/EXTERNAL authentication started SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth SASL SSF: 0 modifying entry "cn={17}dns-fd,cn=schema,cn=config" ldap_modify: Other (e.g., implementation specific) error (80) additional info: olcObjectClasses: AttributeType not found: "fdDNSViewAclName"
(from redmine: written on 2016-03-10)
added Added label
