BIND 10 #2580: warn inconsistent RR TTLs on zone loading

[BIND 10 Development]

#2580: warn inconsistent RR TTLs on zone loading
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:
  jinmei                             |                Status:  new
                       Type:  task   |             Milestone:  New Tasks
                   Priority:         |              Keywords:
  medium                             |             Sensitive:  0
                  Component:  data   |           Sub-Project:  DNS
  source                             |  Estimated Difficulty:  0
               CVSS Scoring:         |           Total Hours:  0
            Defect Severity:  N/A    |
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
 See http://bind10.isc.org/ticket/2470#comment:13

 Currently, we ignore inconsistent TTLs for RRs of the same RRset
 on loading.  The minimum TTL will be silently used for the in-memory
 case; in the case of database-based data sources, a warning will be
 logged at the time of lookup, but the operator cannot notice it until
 then.

 As discussed in the above link, there didn't seem to be an easy
 solution.  It's also related to a higher level discussion on
 where/how we do some kinds of checks, especially if they may not be
 effectively doable in the post-loading validation phase.

 This ticket is probably non-estimatable until these points are
 clarified.

-- 
Ticket URL: <http://bind10.isc.org/ticket/2580>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development