BIND 10 #389: Configuration of b10-recurse trough the config manager
BIND 10 Development
do-not-reply at isc.org
Tue Oct 26 08:27:17 UTC 2010
#389: Configuration of b10-recurse trough the config manager
---------------------------+------------------------------------------------
Reporter: vorner | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: Unclassified | Keywords:
Sensitive: 0 | Estimatedhours: 0
Hours: 0 | Billable: 1
Totalhours: 0 | Internal: 0
---------------------------+------------------------------------------------
I modified the b10-recurse to be configured by the config manager. It is
possible to configure the addresses and ports it listens on and the
addresses it forwards queries to. If it has no address to forward to, it
is in recursive mode, if it has, it is in forward mode.
It still has the -u and -v parameters. Currently, verboseness is global
setting for single run of bind10 and will probably stay so until logging
system is created. The -u will be dropped, since changing user is job for
boss, not separate processes.
The bind10 still takes -f to tell it to run recurse instead of auth,
changing this is a different task.
There are two problems. One is, it is impossible to change the listening
sockets at runtime, as it is not possible to close the current ones
(#388). The second is it is not possible to change the configuration
trough bindctl, it doesn't handle properly configuring maps inside lists
(#384). I suggest this should be left as separate tasks and this one
revied and merged back to branches/trac327.
The current code is in branches/vorner-recursor-config, between r3317 to
r3353.
I propose this changelog entry:
{{{
[func] vorner
The b10-recursive is configured trough config manager.
It has "listen_on" and "forward_addresses" options.
(trac389, SVN rTBD)
}}}
--
Ticket URL: <http://bind10.isc.org/ticket/389>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list