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:  defect    |                Status:  new
                   Priority:  major     |             Milestone:  New Tasks
                  Component:  b10-auth  |            Resolution:
                   Keywords:            |             Sensitive:  0
            Defect Severity:  N/A       |           Sub-Project:  DNS
Feature Depending on Ticket:            |  Estimated Difficulty:  0
        Add Hours to Ticket:  0         |           Total Hours:  0
                  Internal?:  0         |
----------------------------------------+----------------------------------

Comment (by jreed):

 Here is another example where earlier ERROR causes wrong config to be
 used:

 {{{
 2012-02-22 15:32:19.216 INFO  [b10-auth.auth] AUTH_SERVER_CREATED server
 created
 2012-02-22 15:32:19.225 ERROR [b10-auth.auth] AUTH_CONFIG_UPDATE_FAIL
 update of configuration failed: Server configuration failed: Invalid RR
 text at line 19: attempt to decode a value not in base64 char set
 2012-02-22 15:32:19.255 INFO  [b10-boss.boss] BIND10_SOCKET_GET requesting
 socket [::]:53 of type TCP from the creator
 2012-02-22 15:32:19.255 ERROR [b10-boss.boss] BIND10_SOCKET_ERROR error on
 bind call in the creator: 13/Permission denied
 2012-02-22 15:32:19.257 ERROR [b10-auth.server_common]
 SRVCOMM_ADDRESS_FAIL failed to listen on addresses ("Error creating socket
 on bind")
 2012-02-22 15:32:19.257 ERROR [b10-auth.auth] AUTH_CONFIG_LOAD_FAIL load
 of configuration failed: Server configuration failed: "Error creating
 socket on bind"
 }}}

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