Bug 788127 - domain names are not expanded with psearch enabled
Summary: domain names are not expanded with psearch enabled
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: bind-dyndb-ldap
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Adam Tkac
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-07 14:56 UTC by Petr Spacek
Modified: 2013-04-30 23:51 UTC (History)
3 users (show)

Fixed In Version: bind-dyndb-ldap-1.1.0-0.8.a2.fc16
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-01 09:28:45 UTC
Type: ---


Attachments (Terms of Use)

Description Petr Spacek 2012-02-07 14:56:36 UTC
Description of problem:
Domain names (from sRVRecord and cNAMERecord attribute) which do not end with a period aren't expanded, if persistent search is enabled (arg "psearch yes").


Version-Release number of selected component (if applicable):
bind-9.8.2-0.2.rc1.fc16.x86_64
bind-dyndb-ldap-1.1.0-0.6.a1.fc16.x86_64

How reproducible:


Steps to Reproduce:
1. in named.conf inside dynamic-db "ipa" section set arg "psearch yes";
2. reload BIND: rndc reload
3. ipa dnsrecord-add idm.lab.bos.redhat.com test --cname-rec vm-042
4. # dig @127.0.0.1 test.idm.lab.bos.redhat.com cname
  

Actual results: ("test" CNAME is not expanded to "test.idm.lab.bos.redhat.com.")
; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.2.rc1.fc16 <<>> @127.0.0.1 test.idm.lab.bos.redhat.com cname
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 53503
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1

;; QUESTION SECTION:
;test.idm.lab.bos.redhat.com.	IN	CNAME

;; ANSWER SECTION:
test.idm.lab.bos.redhat.com. 86400 IN	CNAME	vm-042.

;; AUTHORITY SECTION:
idm.lab.bos.redhat.com.	86400	IN	NS	vm-042.idm.lab.bos.redhat.com.

;; ADDITIONAL SECTION:
vm-042.idm.lab.bos.redhat.com. 86400 IN	A	10.16.78.42



Expected results: ("test" CNAME IS expanded to "test.idm.lab.bos.redhat.com.")
; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.2.rc1.fc16 <<>> @127.0.0.1 test.idm.lab.bos.redhat.com cname
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20287
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1

;; QUESTION SECTION:
;test.idm.lab.bos.redhat.com.	IN	CNAME

;; ANSWER SECTION:
test.idm.lab.bos.redhat.com. 86400 IN	CNAME	vm-042.idm.lab.bos.redhat.com.

;; AUTHORITY SECTION:
idm.lab.bos.redhat.com.	86400	IN	NS	vm-042.idm.lab.bos.redhat.com.

;; ADDITIONAL SECTION:
vm-042.idm.lab.bos.redhat.com. 86400 IN	A	10.16.78.42

Comment 2 Fedora Update System 2012-02-13 17:46:18 UTC
bind-dyndb-ldap-1.1.0-0.8.a2.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/bind-dyndb-ldap-1.1.0-0.8.a2.fc16

Comment 3 Fedora Update System 2012-02-13 17:46:37 UTC
bind-dyndb-ldap-1.1.0-0.8.a2.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/bind-dyndb-ldap-1.1.0-0.8.a2.fc15

Comment 4 Fedora Update System 2012-02-14 09:00:27 UTC
Package bind-dyndb-ldap-1.1.0-0.8.a2.fc15:
* should fix your issue,
* was pushed to the Fedora 15 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing bind-dyndb-ldap-1.1.0-0.8.a2.fc15'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-1601/bind-dyndb-ldap-1.1.0-0.8.a2.fc15
then log in and leave karma (feedback).

Comment 5 Fedora Update System 2012-03-01 09:28:45 UTC
bind-dyndb-ldap-1.1.0-0.8.a2.fc15 has been pushed to the Fedora 15 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 6 Fedora Update System 2012-03-01 09:34:38 UTC
bind-dyndb-ldap-1.1.0-0.8.a2.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.