Learn more about these different git repos.
Other Git URLs
Current record format in LDAP is less powerful than BIND's. Generally, each RRset can have own TTL value, see [2181 section 5.2]]([http://tools.ietf.org/html/rfc2181#section-5.2|RFC).
We allow only single value per name, so it's not possible to have e.g. single name with long-term A record and short term LOC record.
It probably leads to some performance degradation in some special cases, but generally it's not a problem. I think it's very-long-term "nice to have".
Maybe we might add record type as LDAP sub-type to DNSTTL attribute and use non-subtyped DNSTTL as default value for whole DNS name.
JHogarth from community wants to implement this: https://www.redhat.com/archives/freeipa-users/2013-July/msg00135.html
[1035]] section 5.1 was amended by [http://tools.ietf.org/html/rfc2181#section-5.2|RFC 2181 section 5.2].
No need to clone deferred tickets to downstream.
Proper handling of modifications to default DNS TTL will likely require additional metadata. See [[Design/MetaDB]].
Metadata Update from @pspacek: - Issue assigned to atkac - Issue set to the milestone: The Deferred
Login to comment on this ticket.