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 733711 - [RFE] Implement full persistent search for DNS
Summary: [RFE] Implement full persistent search for DNS
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: bind-dyndb-ldap
Version: 6.3
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Adam Tkac
QA Contact: Namita Soman
URL: https://fedorahosted.org/bind-dyndb-l...
Whiteboard:
Depends On: 767496 802375
Blocks: 756082 767486 827414
TreeView+ depends on / blocked
 
Reported: 2011-08-26 15:09 UTC by Martin Kosek
Modified: 2013-11-21 20:02 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Release Note
Doc Text:
Full Persistent Search for DNS LDAP in Red Hat Enterprise Linux 6.4 includes support for persistent search for both zones and their resource records. Persistent search allows the bind-dyndb-ldap plug-in to be immediatelly informed about all changes in an LDAP database. It also decreases network bandwidth usage required by repeated polling.
Clone Of:
Environment:
Last Closed: 2013-02-21 08:57:34 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 689637 1 None None None 2021-01-20 06:05:38 UTC
Red Hat Product Errata RHBA-2013:0359 0 normal SHIPPED_LIVE bind-dyndb-ldap bug fix and enhancement update 2013-02-20 20:53:11 UTC

Internal Links: 689637

Description Martin Kosek 2011-08-26 15:09:46 UTC
Description of problem:

Right now upstream bind-dyndb-ldap supports persistent search only for zones. That allows the name server to immediately read new/modified DNS zones when they are added/removed from LDAP.

We would need to extend this feature also for DNS records so that records in given zone (for example A record for foo.example.com in zone example.com) or records directly in zone (for example MX record directly in zone example.com) are immediately loaded when they are changed in LDAP.

Actual results:
Record is changed but its resolvable after the record validity expires.

Expected results:
Changed record is immediately res

Additional info:

Comment 4 Martin Kosek 2011-08-31 20:58:52 UTC
This bug has been created as a RFE based on #689637 which has been fixed as documentation fix for now. This new feature would enable us to have a more convenient solution for the users and have any changed DNS record immediately resolvable (and do not have to wait for bind-dyndb-ldap cache ttl).

Comment 5 Martin Kosek 2011-08-31 21:04:17 UTC
Update for the state of the current upstream persistent search feature:

The zone-only persistent search has been improved so that DNS records directly in the zone (MX record directly in zone example.com) as in

https://bugzilla.redhat.com/show_bug.cgi?id=689637

are updated in the name server immediately. This would solve 689637 (and its duplicates) completely when released for RHEL. Implementing a full persistent search would allow us to get immediate changes not only for zone records, but standard records too.

Comment 13 Martin Kosek 2012-05-22 10:31:09 UTC
Fixed upstream:
master: https://fedorahosted.org/freeipa/changeset/9a5c2090eb996f131a6d96e997b0db8e762716ba

Comment 14 Martin Kosek 2012-05-22 10:33:24 UTC
Moving back to ASSIGNED, I did not notice that this upstream ticket is just a part of solution.

Comment 16 Martin Kosek 2012-06-04 15:04:38 UTC
Upstream ticket:
https://fedorahosted.org/bind-dyndb-ldap/ticket/73

Comment 21 Namita Soman 2012-11-16 20:02:32 UTC
Verified using:
ipa-server-3.0.0-8.el6.x86_64


tests for psearch pass:
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:: [   LOG    ] :: ipa-dns-psearch-01 psearch is enabled when ipa server is installed
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

:: [   PASS   ] :: File '/etc/named.conf' should contain 'psearch yes'
:: [   LOG    ] :: Duration: 0s
:: [   LOG    ] :: Assertions: 1 good, 0 bad
:: [   PASS   ] :: RESULT: ipa-dns-psearch-01 psearch is enabled when ipa server is installed

::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:: [   LOG    ] :: ipa-dns-psearch-02 create a new zone and check the zone with dig
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

:: [   LOG    ] :: Executing: ipa dnszone-add --name-server=ipaqavmh.testrelm.com. --admin-email=ipaqar.redhat.com --serial=2010010701 --refresh=303 --retry=101 --expire=1202 --minimum=33 --ttl=55 westford.testrelm.com
:: [   PASS   ] :: Create a new zone
:: [   LOG    ] :: Executing: dig westford.testrelm.com SOA | grep NS | grep ipaqavmh.testrelm.com.
:: [   PASS   ] :: checking with dig to ensure that the new zone got created with the correct name server
:: [   LOG    ] :: Duration: 3s
:: [   LOG    ] :: Assertions: 2 good, 0 bad
:: [   PASS   ] :: RESULT: ipa-dns-psearch-02 create a new zone and check the zone with dig

::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:: [   LOG    ] :: ipa-dns-psearch-03 add record of type txt and check the record with dig
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

:: [   LOG    ] :: Executing: ipa dnsrecord-add westford.testrelm.com txt --txt-rec none=1.2.3.4
:: [   PASS   ] :: add record type txt
:: [   LOG    ] :: Executing: dig txt.westford.testrelm.com TXT | grep none=1.2.3.4
:: [   PASS   ] :: make sure dig can find the txt record
:: [   LOG    ] :: Duration: 2s
:: [   LOG    ] :: Assertions: 2 good, 0 bad
:: [   PASS   ] :: RESULT: ipa-dns-psearch-03 add record of type txt and check the record with dig

::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:: [   LOG    ] :: ipa-dns-psearch-04 update record's txt value and check using dig
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

:: [   LOG    ] :: Executing: ipa dnsrecord-mod westford.testrelm.com txt --txt-rec=none=1.2.3.4 --txt-data=newip=5.6.7.8
:: [   PASS   ] :: modify record type txt
:: [   LOG    ] :: Executing: dig txt.westford.testrelm.com TXT | grep newip=5.6.7.8
:: [   PASS   ] :: make sure dig can find updated txt record
:: [   LOG    ] :: Duration: 3s
:: [   LOG    ] :: Assertions: 2 good, 0 bad
:: [   PASS   ] :: RESULT: ipa-dns-psearch-04 update record's txt value and check using dig

::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:: [   LOG    ] :: ipa-dns-psearch-05 update record's txt value again and check zone has a new serial that is higher than previous serial
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

:: [   LOG    ] :: Executing: ipa dnsrecord-mod westford.testrelm.com txt --txt-rec=newip=5.6.7.8 --txt-data=newip=8.7.6.5
:: [   PASS   ] :: update record type txt
:: [   PASS   ] :: new serial after updating record is higher. Was: 2010010704; New: 2010010705
:: [   LOG    ] :: Duration: 2s
:: [   LOG    ] :: Assertions: 2 good, 0 bad
:: [   PASS   ] :: RESULT: ipa-dns-psearch-05 update record's txt value again and check zone has a new serial that is higher than previous serial

Comment 23 errata-xmlrpc 2013-02-21 08:57:34 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.

http://rhn.redhat.com/errata/RHBA-2013-0359.html


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