RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1183805 - Documentation for setting multiple values for idnsAllowTransfer idnsAllowQuery is incorrect.
Summary: Documentation for setting multiple values for idnsAllowTransfer idnsAllowQuer...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: bind-dyndb-ldap
Version: 6.6
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: rc
: ---
Assignee: Petr Spacek
QA Contact: Namita Soman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-01-19 21:15 UTC by Clifton Coursey
Modified: 2019-07-11 08:33 UTC (History)
3 users (show)

Fixed In Version: bind-dyndb-ldap-2.3-7.el6
Doc Type: Bug Fix
Doc Text:
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.
Clone Of:
Environment:
Last Closed: 2015-07-22 05:39:18 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 1315883 0 None None None Never
Red Hat Product Errata RHBA-2015:1259 0 normal SHIPPED_LIVE bind-dyndb-ldap bug fix update 2015-07-20 17:49:53 UTC

Description Clifton Coursey 2015-01-19 21:15:58 UTC 
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):
bind-dyndb-ldap-2.3


Additional info:
/usr/share/doc/bind-dyndb-ldap-2.3/README
Comment 1 Clifton Coursey 2015-01-19 21:40:11 UTC 
Here is the delta:
<snip>
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.

        Example:
                idnsAllowQuery: 127.0.0.1
                idnsAllowQuery: ::1
                idnsAllowQuery: 192.168.1.0/24

        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
</snip>

NEEDS TO BE:

idnsAllowQuery: 10.14.7.222;10.14.5.171;10.14.5.172;10.14.5.173;!10.0.0.0/8;

[+] Knowledge Base Solution/Article created for the same
Comment 4 Petr Spacek 2015-01-20 08:40:47 UTC 
Upstream ticket:
https://fedorahosted.org/bind-dyndb-ldap/ticket/154
Comment 5 Petr Spacek 2015-01-21 14:17:04 UTC 
Fixed upstream: https://fedorahosted.org/bind-dyndb-ldap/changeset/a4565b3ef843e4464d2e950f0716818e7c7ce09b/
Comment 7 Kaleem 2015-05-28 10:18:04 UTC 
Verified.

[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.

* idnsAllowQuery
	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
	are allowed.

	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.

* idnsAllowTransfer
[root@dhcp207-230 ~]# rpm -q bind-dyndb-ldap
bind-dyndb-ldap-2.3-7.el6.x86_64
[root@dhcp207-230 ~]#
Comment 9 errata-xmlrpc 2015-07-22 05:39:18 UTC 
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.

https://rhn.redhat.com/errata/RHBA-2015-1259.html
Note You need to log in before you can comment on or make changes to this bug.