BIND 10 #337: Expired zone should not be served

[BIND 10 Development]

#337: Expired zone should not be served
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  jinmei
  zhanglikun                         |                Status:  assigned
                       Type:         |             Milestone:  Year 3 Task
  defect                             |  Backlog
                   Priority:  major  |            Resolution:
                  Component:         |             Sensitive:  0
  Unclassified                       |           Sub-Project:  DNS
                   Keywords:         |  Estimated Difficulty:  3.0
            Defect Severity:  N/A    |           Total Hours:  0
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by jinmei):

 Replying to [comment:9 shane]:
 > Jinmei, we've refactored the data sources. Is there any action taken now
 when a zone becomes stale? If so, I guess we can resolve this ticket.
 Otherwise we need to implement it! :)

 In terms of the new data source API/implementation, we don't do
 anything about expired zone.  IMO it's more about another ever-lasting
 topic of zone configuration/management redesign, rather than
 manipulating zone data in a data source.

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