#2558 [RFE] Make LDAP DNS schema flexible as BIND zone files
Closed: Invalid None Opened 12 years ago by dpal.

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.

Discussion over this was had here:

https://www.redhat.com/archives/freeipa-users/2013-July/msg00135.html

I was considering this in scope for the general TTL refactor but the cost in complexity versus the actual use case was not considered worth it at this time.

Hello.

Based on a long discussion, FreeIPA team recently revised Goals and Assumptions of the DNS component in IPA/IdM:

Based on the information linked from that page, FreeIPA team decided that support for this feature directly does not really fit our direction and should be resolved in other way. I am therefore closing this request as WONTFIX.

Some related use-cases might be covered by ticket:4424.

Have a nice day.

Metadata Update from @dpal:
- Issue assigned to someone
- Issue set to the milestone: Tickets Deferred

7 years ago

Login to comment on this ticket.

Metadata