BIND 10 #2113: Configuration plugin check for datasources

[BIND 10 Development]

#2113: Configuration plugin check for datasources
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  vorner
  vorner                             |                Status:  reviewing
                       Type:         |             Milestone:
  defect                             |  Sprint-20120807
                   Priority:         |            Resolution:
  medium                             |             Sensitive:  0
                  Component:         |           Sub-Project:  DNS
  configuration                      |  Estimated Difficulty:  5
                   Keywords:         |           Total Hours:  0
            Defect Severity:  N/A    |
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Changes (by jelte):

 * owner:  jelte => vorner


Comment:

 Replying to [comment:7 vorner]:
 > > I think the error string in case of bad classes could be better; it
 prints "Unrecognized RR parameter string" which isn't really helpful IMO.
 >
 > Is it better now?
 >

 yes :) thanks

 >
 > Yes, that's correct ‒ the config manager has the cache disabled,
 therefore it warns. But the auth has it enabled and it serves it.
 >
 > But I don't think it is a good idea to enable the cache in the
 configuration manager, because then, it would take a long time to load it
 (imagine a very large zone) and then it would just throw it away anyway.
 >
 > So, what do we do about the warning? I probably could mangle the
 configuration to not contain the zones and check them manually only. Would
 that be OK or does it sounds like too much of a hack?

 I was about to say that i'd prefer some form of 'dry run', where
 everything is checked but not actually loaded. But I guess that is the
 whole purpose of the config plugin in the first place.

 Since masterfiles is already treated as a special case, could we just
 check whether the files exist and are readable (and not pass it to
 configure() if type is masterfiles)? Masterfiles is already special-cased
 in both the checker plugin and the client list.

 Of course, that is assuming that this is the only one where caching is
 needed to serve something at all.

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