BIND 10 #1707: Default configuration was used when mistake in different configuration

[BIND 10 Development]

#1707: Default configuration was used when mistake in different configuration
-------------------------------------+-------------------------------------
                   Reporter:  jreed  |                 Owner:
                       Type:         |                Status:  new
  defect                             |             Milestone:
                   Priority:         |  Sprint-20120403
  medium                             |            Resolution:
                  Component:         |             Sensitive:  0
  b10-auth                           |           Sub-Project:  DNS
                   Keywords:         |  Estimated Difficulty:  4
            Defect Severity:  Very   |           Total Hours:  0
  High                               |
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by jinmei):

 Replying to [comment:7 jelte]:

 > As for this problem, I'm a bit confused; if a filename just got changed,
 and the listen ports were left as they were, it shouldn't touch those. If
 both are changed then it should reject both if one contains a problem. On
 startup, this is always the case; all existing settings are considered one
 change that either works or does not work (and then it would indeed fall
 back to 53 if another part contains an error).

 First off, this is about the startup case (as I understand it).

 And, since there's an error in the zone file name, both the file name
 and listen_on configurations are ignored, and fall back to the default
 listen_on.  If that's what you meant above, your understanding of
 what's happening is correct.

 So the confusion is about whether this is a problem?  I think it is,
 because the admin may have never wanted the default setting (e.g. the
 intended configuration may be to restrict the access quite tightly and
 the admin may not want to allow access from any even for a very short
 period until they notice the error).  This is different from the case
 of updating an existing config - in that case, the previous one was at
 least once intended, and until the update is completed successfully it
 makes sense to keep that configuration.

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