Part of the issue here is that they really are several individual A (or AAAA) records, with the imposed constraint that the TTL for all RRs of a given type MUST be identical. When you add in that several of the RRs are added dynamically as the node is deployed, it gets even more interesting.
Perhaps just a warning when the user goes to edit the TTL telling him that it will change all of that RRtype? (A an AAAA can have different TTLs, of course.)
Part of the issue here is that they really are several individual A (or AAAA) records, with the imposed constraint that the TTL for all RRs of a given type MUST be identical. When you add in that several of the RRs are added dynamically as the node is deployed, it gets even more interesting.
Perhaps just a warning when the user goes to edit the TTL telling him that it will change all of that RRtype? (A an AAAA can have different TTLs, of course.)