BIND 10 #662: b10-auth wrongly falls back to default listen_on

[BIND 10 Development]

#662: b10-auth wrongly falls back to default listen_on
----------------------------------------+---------------------------------
                   Reporter:  jreed     |                 Owner:  jreed
                       Type:  defect    |                Status:  assigned
                   Priority:  medium    |             Milestone:
                  Component:  b10-auth  |            Resolution:
                   Keywords:            |             Sensitive:  0
            Defect Severity:  Medium    |           Sub-Project:  DNS
Feature Depending on Ticket:            |  Estimated Difficulty:  0.0
        Add Hours to Ticket:  0         |           Total Hours:  0
                  Internal?:  0         |
----------------------------------------+---------------------------------

Comment (by jreed):

 I hit this problem again. This time with b10-resolver. I had four
 listen_on configurations (which includes two localhost addresses). Due to
 configuration error (outside of BIND 10), a wrong inet6 address was
 configured. The socket creation/binding error was logged a few times (but
 didn't identify the problem, see #1946). This made me think that the next
 listen_on as skipped and the third and fourth entries were used. Now I
 realize all were skipped on the first's failure. Just the default
 configuration was used.

 The default configuration should not be used.  If we do decide to use
 default configuration for some things, it needs to be clearly logged.

 Maybe this ticket is related to #1707?

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