BIND 10 #1733: wrong configurations used, confusion on startup order

[BIND 10 Development]

#1733: wrong configurations used, confusion on startup order
-------------------------------------+-------------------------------------
            Reporter:  jreed         |                        Owner:
                Type:  defect        |                       Status:  new
            Priority:  major         |                    Milestone:  New
           Component:  Unclassified  |  Tasks
           Sensitive:  0             |                     Keywords:
         Sub-Project:  DNS           |              Defect Severity:  N/A
Estimated Difficulty:  0             |  Feature Depending on Ticket:
         Total Hours:  0             |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
 Maybe related to #1707 but in this case I don't see any configuration
 confusion (no mistakes and no errors in logs about it).

 I have both auth and resolver components configured.

 The auth server is configured with:

 {{{
 > config show Auth/listen_on
 Auth/listen_on[0]/address       "::"    string
 Auth/listen_on[0]/port  5300    integer
 Auth/listen_on[1]/address       "0.0.0.0"       string
 Auth/listen_on[1]/port  5300    integer
 }}}

 But listening on:

 {{{
  root     b10-auth   12084 12 tcp6   *.53                  *.*
 root     b10-auth   12084 13 udp6   *.53                  *.*
 root     b10-auth   12084 14 tcp    *.53                  *.*
 root     b10-auth   12084 15 udp    *.53                  *.*
 root     python3.1  21055 18 tcp6   *.53                  *.*
 root     python3.1  21055 20 udp6   *.53                  *.*
 root     python3.1  21055 21 tcp    *.53                  *.*
 root     python3.1  21055 22 udp    *.53                  *.*
 }}}
 21055 is my boss. Notice 53 instead of 5300.
 Well my resolver does want 53, but fails:

 {{{
 2012-02-29 15:12:41.493 ERROR [b10-boss.boss] BIND10_SOCKET_ERROR error on
 bind call in the creator: 48/Address already in use
 ...
 2012-02-29 15:12:41.559 ERROR [b10-auth.server_common]
 SRVCOMM_ADDRESS_FAIL failed to listen on addresses ("Error creating socket
 on bind")
 2012-02-29 15:12:41.559 ERROR [b10-resolver.resolver]
 RESOLVER_CONFIG_ERROR error in configuration: "Error creating socket on
 bind"
 }}}

 I tricked it to work by simply doing:
 {{{
 > Resolver shutdown
 > Auth shutdown
 }}}

 Then my resolver was listening on 53 and auth on 5300 (like I wanted).

-- 
Ticket URL: <http://bind10.isc.org/ticket/1733>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development