Authoritative DNS setup in BIND10

[Jeremy C. Reed]

On Wed, 17 Jul 2013, Michal 'vorner' Vaner wrote:

> > I am also not able to find any script to stop the bind10 in one go. (i
> > run the bind10 script in background and it starts multiple
> > thread/scripts for multiple task. Now i am not able to stop bind10 in
> > one go. I am killing each task manually to stop bind10 completely).
> 
> You can either issue `Init shutdown` in bindctl, or just kill the ?main? process
> of bind10 (`killall b10-init` would do). It'll bring down the rest.

Be careful, on some systems (like Solaris) "killall" means "kill all". 
(I haven't tried lately so not sure what will happen with the bogus 
argument.)

> > One more issue which i am facing is, b10-cmdctl is listening on
> > 127.0.0.1. I want to change it to listen on all the interfaces
> > configured on the server.
> > I tried to run "./b10-cmdctl -a x.x.x.x" but it is giving me an error.
> > I want to configure it globally so as to listen b10-cmdctl on 0.0.0.0.
> > Any suggestion how to do that.
> 
> You're not supposed to run these internal programs manually, they 
> expect some special environment passed from the b10-init that starts 
> them.
> 
> Looking around, it seems to be possible to set the port on the bind10 
> command line, but not the address, it seems forgotten. Would you mind 
> opening a bug about that one?

We have a ticket for it:

http://bind10.isc.org/ticket/656