BIND 10 #2421: don't reject configuring entire inmemory datasrc due to one broken zone

[BIND 10 Development]

#2421: don't reject configuring entire inmemory datasrc due to one broken zone
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:
  jinmei                             |                Status:  new
                       Type:         |             Milestone:  Next-Sprint-
  defect                             |  Proposed
                   Priority:  high   |            Resolution:
                  Component:  data   |             Sensitive:  0
  source                             |           Sub-Project:  DNS
                   Keywords:         |  Estimated Difficulty:  0
            Defect Severity:  N/A    |           Total Hours:  0
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Description changed by jinmei:

Old description:

> We currently reject configuring a data source (with in-memory cache)
> if loading one particular zone fails.  That's probably not a good
> behavior, and is at least incompatible with BIND 9.  BIND 9 simply
> marks it as a bad zone and returns SERVFAIL to queries to that zone,
> still loading and serving any other valid zones.
>
> I think that's more reasonable behavior, and I believe it's not very
> difficult to implement it.  So I suggest we fix it now.
>
> It's also related to an issue reported by a user.

New description:

 We currently reject configuring a data source (with in-memory cache)
 if loading one particular zone fails.  That's probably not a good
 behavior, and is at least incompatible with BIND 9.  BIND 9 simply
 marks it as a bad zone and returns SERVFAIL to queries to that zone,
 still loading and serving any other valid zones.

 I think that's more reasonable behavior, and I believe it's not very
 difficult to implement it.  So I suggest we fix it now.

 It's also related to an issue reported by a user.

 See also #1932.  In that ticket I hinted deferring it until we
 complete the generic loader work, but with the understanding of the
 most recent code I think it can be done separately from the loader,
 i.e., just updating the `ConfigurableClientList` class.

--

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