Hide Forgot
This bug is created as a clone of upstream ticket: https://fedorahosted.org/freeipa/ticket/2558 {{{ Description of problem: Current record format in LDAP is less powerful than BIND's. Generally, each record (not only name) can have own TTL value, see RFC1035 http://tools.ietf.org/html/rfc1035 section 5.1. We allow only single TTL value per name, so it's not possible to have e.g. single name with long-term A record and short term LOC record. IPA LDAP schema should be as powerfull as BIND zone files. Version-Release number of selected component (if applicable): 2.1.3-9.el6 How reproducible: Add two records with different same DNS name and different TTL. Steps to Reproduce: 1. ipa dnsrecord-add --ttl=123 localnet r1 --a-rec=1.2.3.4 2. ipa dnsrecord-add --ttl=555 localnet r1 --txt-rec=TEST Actual results: # ipa dnsrecord-add --ttl=123 localnet r1 --a-rec=1.2.3.4 Record name: r1 Time to live: 123 A record: 1.2.3.4 # ipa dnsrecord-add --ttl=555 localnet r1 --txt-rec=TEST Record name: r1 Time to live: 123 A record: 1.2.3.4 TXT record: TEST Expected results: # ipa dnsrecord-add --ttl=123 localnet r1 --a-rec=1.2.3.4 Record name: r1 Time to live: 123 A record: 1.2.3.4 # ipa dnsrecord-add --ttl=555 localnet r1 --txt-rec=TEST Record name: r1 Time to live: 555 A record: 1.2.3.4 TXT record: TEST Additional info: Big schema & UI & BIND LDAP plugin change is required. }}}
Thank you taking your time and submitting this request for Red Hat Enterprise Linux. Unfortunately, this bug was not given a priority and was deferred both in the upstream project and in Red Hat Enterprise Linux. Given that we are unable to fulfill this request in following Red Hat Enterprise Linux releases, I am closing the Bugzilla as DEFERRED. To request that Red Hat re-considers the decision, please re-open the Bugzilla via appropriate support channels and provide additional business and/or technical details about its importance to you. Note that you can still track this request or even contribute patches in the referred upstream Trac ticket.