BIND 10 #2173: AUTH_COMMAND_FAILED execution of command channel instruction 'loadzone' failed: There's no client list for class IN

[BIND 10 Development]

#2173: AUTH_COMMAND_FAILED execution of command channel instruction 'loadzone'
failed: There's no client list for class IN
-------------------------------------+-------------------------------------
                   Reporter:  shane  |                 Owner:
                       Type:         |                Status:  new
  defect                             |             Milestone:  Next-Sprint-
                   Priority:         |  Proposed
  medium                             |            Resolution:
                  Component:         |             Sensitive:  0
  Unclassified                       |           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      |
-------------------------------------+-------------------------------------

Comment (by vorner):

 I'd like to explain what happened and that maybe we may not want to do
 anything about this.

 We switched to new configuration for data sources, in /data_sources. At
 the time of this ticket, the default for this is empty list of data
 sources, which means auth knows no zones at all.

 However, the XfrIn uses the old configuration ‒ Auth/database_file, which
 points to a database containing some zones. So it happily transfered a
 zone in and went to notify auth about it. Auth does not find the zone and
 correctly errors on it. This happens because of the inconsistency of zones
 XfrIn and Auth know.

 The first thing to lower the risk of this is when we merge #2133. That one
 changes the new default to match the old default, so the default
 configuration does not contain any inconsistency and the administrator
 would have to create it manually. The second and final thing is moving
 XfrIn to use the same configuration (#2129). Then it will be impossible
 for the inconsistency exist.

 And I don't think either XfrIn nor Auth would be misbehaving. XfrIn
 correctly notifies about new zone data. Auth correctly tells it it's being
 mad and that there is no data source at all to contain the zone. Such
 problem in configuration definitely deserves to have an ERROR log message.

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