Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 918697

Summary: IP lookup failing with multiple DNS entries
Product: Red Hat Enterprise Linux 7 Reporter: Nathan Kinder <nkinder>
Component: 389-ds-baseAssignee: Rich Megginson <rmeggins>
Status: CLOSED CURRENTRELEASE QA Contact: Sankar Ramalingam <sramling>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 7.0CC: amsharma, jgalipea, mgregg, nhosoi, sramling
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 389-ds-base-1.3.1.2-1.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-13 09:44:21 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Nathan Kinder 2013-03-06 18:14:27 UTC
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/311

Hello.

Version: CDS 8.2 i386

Setup: User authentication using Host Access Permissions.

Issue:

When a client has multiple hostnames in DNS the LDAP gets confused because nslookup returns multiple DNS entries for the same client IP. These entries rotate in the output of nslookup, thus causing logins to be denied. Should LDAP scrape the nslookup output for the hostname?

ReCreate:

From the Console add a user and enable Posix user Attributes.
Right click on the new user and select "Set Access Permissions...".
Create new entry and under the "Hosts" tab Add the "DNS host filter:"

*Make sure the host has multiple entries in DNS and that they rotate when doing an nslookup on the IP.

Comment 1 Rich Megginson 2013-10-01 23:26:08 UTC
moving all ON_QA bugs to MODIFIED in order to add them to the errata (can't add bugs in the ON_QA state to an errata).  When the errata is created, the bugs should be automatically moved back to ON_QA.

Comment 3 Amita Sharma 2014-01-08 07:44:48 UTC
Hi Noriko,

Request you to please add verification steps from command line.
Should I make use of dnsalias keyword in ACI and use something like ::
aci: (targetattr = "*") (version 3.0;acl "dnsalias example";allow (all)
 dns="hostA.example.com" or dnsalias="hostB.example.com" or dnslias=
 "hostC.example.com";) ?

Thanks,
Ami

Comment 4 Noriko Hosoi 2014-01-13 17:57:19 UTC
(In reply to Amita Sharma from comment #3)
> Hi Noriko,
> 
> Request you to please add verification steps from command line.
> Should I make use of dnsalias keyword in ACI and use something like ::
> aci: (targetattr = "*") (version 3.0;acl "dnsalias example";allow (all)
>  dns="hostA.example.com" or dnsalias="hostB.example.com" or dnslias=
>  "hostC.example.com";) ?

Hi Ami, 

That's correct.  You are supposed to have a host which has multiple host names associated with.  And let nslookup return non-FQDN hostname (hostB.example.com or hostC.example.com in the above ACI sample).  Accessing the DS from the client host used to fail with this ACI "aci: (targetattr = "*") (version 3.0;acl "...";allow (all) dns="hostA.example.com";)  (Note: there was no dnsalias keyword available before.)  But with the ACI you put in the comment3, the requests from the client host are always allowed.

Comment 12 Amita Sharma 2014-01-27 07:42:53 UTC
[root@dhcp201-149 export]# rpm -qa | grep 389
389-adminutil-1.1.15-3.fc19.1.x86_64
389-ds-base-debuginfo-1.3.1.6-15.el7.x86_64
389-ds-base-libs-1.3.1.6-15.el7.x86_64
389-ds-base-1.3.1.6-15.el7.x86_64
389-console-1.1.7-4.fc19.noarch


[root@dhcp201-149 ~]# nslookup 10.65.201.149
Server:		10.65.201.135
Address:	10.65.201.135#53

149.201.65.10.in-addr.arpa	name = hostB.testzone.com.
149.201.65.10.in-addr.arpa	name = hostC.testzone.com.
149.201.65.10.in-addr.arpa	name = hostA.testzone.com.

[root@dhcp201-149 ~]# nslookup 10.65.201.149
Server:		10.65.201.135
Address:	10.65.201.135#53

149.201.65.10.in-addr.arpa	name = hostC.testzone.com.
149.201.65.10.in-addr.arpa	name = hostA.testzone.com.
149.201.65.10.in-addr.arpa	name = hostB.testzone.com.

[root@dhcp201-149 ~]# nslookup 10.65.201.149
Server:		10.65.201.135
Address:	10.65.201.135#53

149.201.65.10.in-addr.arpa	name = hostA.testzone.com.
149.201.65.10.in-addr.arpa	name = hostB.testzone.com.
149.201.65.10.in-addr.arpa	name = hostC.testzone.com.

[root@dhcp201-149 export]# ldapadd -x -h localhost -p 389 -D "cn=Directory Manager" -w Secret123  << EOF
dn: uid=amsharma1,ou=people,dc=example,dc=com
cn: ams
sn: ams
givenname: ams
objectclass: top
objectclass: person
objectclass: organizationalPerson
objectclass: inetOrgPerson
uid: ams
mail: ams
userpassword: amsamsams
aci: (targetattr = "*") (version 3.0;acl "dnsalias example";allow (all) dns="hostA.example.com" or dnsalias="hostB.example.com" or dnslias="hostC.example.com";)
EOF

ldapsearch -x -h 10.16.96.134 -p 389 -D "uid=amsharma1,ou=people,dc=example,dc=com" -w amsamsams -b "ou=people,dc=example,dc=com"

# People, example.com
dn: ou=People,dc=example,dc=com
objectClass: top
objectClass: organizationalunit
ou: People
.
.
.
.

Hence marking as VERIFIED.

Comment 13 Ludek Smid 2014-06-13 09:44:21 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.