BIND 10 #969: non-intuitive bindctl configuration for Auth/listen_on

BIND 10 Development do-not-reply at isc.org
Wed May 25 15:16:09 UTC 2011


#969: non-intuitive bindctl configuration for Auth/listen_on
---------------------------------+-----------------------------------------
            Reporter:  jreed     |                        Owner:
                Type:  defect    |                       Status:  new
            Priority:  minor     |                    Milestone:  New Tasks
           Component:  bind-ctl  |                     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
---------------------------------+-----------------------------------------
 This is a few problems.

 I want to be able to just change one default. Testing as non-root.
 Defaults have port 53 for :: and 127.0.0.1. For testing, I change one to
 5300, but commit fails since the other "default" port 53 still does not
 work:

 {{{

 > config set Auth/listen_on[0]/port 5300
 > config commit
 Setting listen addresses:
  :::5300
  0.0.0.0:53
 Initialize TCP server at :::5300
 Initialize UDP server at :::5300
 Initialize TCP server at 0.0.0.0:53
 Unable to set new address: Failed to initialize network servers:
 Permission denied
 [b10-auth] error: Server configuration failed: Failed to initialize
 network servers: Permission denied
 Error: Server configuration failed: Failed to initialize network servers:
 Permission denied
 Configuration not committed
 }}}

 It seems like if I change one configuration, then that one configuration
 should be used.

 Second problem (starting with my custom config removed so just defaults
 again):

 {{{

 > config remove Auth/listen_on[0]
 > config diff
 {'Auth': {'listen_on': [{'port': 53, 'address': '0.0.0.0'}]}}
 > config set Auth/listen_on[1]/port 5300
 > config diff
 {'Auth': {'listen_on[1]': {'port': 5300}, 'listen_on': [{'port': 53,
 'address': '0.0.0.0'}]}}
 > config commit
 Error: Error in config validation: Unknown item listen_on[1]
 Configuration not committed

 }}}

 I did not immediately realize that listen_on[1] became listen_on[0]

 Comments from jabber follow:

 (09:55:07) vorner: jreed: actually, it created new item called
 listen_on[0], which is a dict and didn't touch the list in listen_on. And
 yes, you confused the poor tool.

 (09:55:56) jelte: well, in this specific case it's not not intuitive, it's
 plain buggy handling that command for an element that doesn't exist

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


More information about the bind10-tickets mailing list