The documentation for bind-dyndb-ldap-2.3 located in the /usr/share/doc/bind-dyndb-ldap-2.3/README file incorrectly stated that the "idnsAllowTransfer" and "idnsAllowQuery" LDAP attributes are multi-valued. Consequently, users were not able to configure DNS zone transfer and query acess control lists according to the documentation. The documentation has been fixed to explain the correct attribute syntax.
Description of problem:
The documentation for bind-dyndb-ldap-2.3 (/usr/share/doc/bind-dyndb-ldap-2.3/README) says that idnsAllowTransfer and idnsAllowQuery allow multiple values, with an example showing multiple values being set, one per line.
ldap_add: Constraint violation (19)
additional info: idnsAllowQuery: multiple values provided
Version-Release number of selected component (if applicable):
Here is the delta:
quote from /usr/share/doc/bind-dyndb-ldap-2.3/README:
This attribute can be set multiple times and are merged together to the one ACL.
In the example above clients with 127.0.0.1 and ::1 IP addresses and
clients from the 192.168.1.0/24 network are allowed to obtain records
from the zone.
# end quote
NEEDS TO BE:
[+] Knowledge Base Solution/Article created for the same
Fixed upstream: https://fedorahosted.org/bind-dyndb-ldap/changeset/a4565b3ef843e4464d2e950f0716818e7c7ce09b/
[root@dhcp207-230 ~]# cat /usr/share/doc/bind-dyndb-ldap-2.3/README |grep "* idnsAllowQuery" -B 2 -A 18
value "dyn_update" from plugin configuration will be used.
Specifies BIND9 zone ACL element as one string.
Example 1: idnsAllowQuery: 192.0.2.1;
In the first example above, only the client with 192.0.2.1 IP address
is allowed to query records from the zone.
Example 2: idnsAllowQuery: !192.0.2.33; 192.0.2.0/24;
In the second example, queries from client 192.0.2.33 are refused
but queries from all other clients in the 192.0.2.0/24 network
You can specify IPv4/IPv6 address, IPv4/IPv6 network address in CIDR
format, and "any" or "none" keywords. The "!" prefix (for example
!192.0.2.33) means negation of the ACL element.
If not set, then zone inherits global allow-query from named.conf.
[root@dhcp207-230 ~]# rpm -q bind-dyndb-ldap
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.