Everything should be set up, and you should be ready to put your new, more
secure BIND into action. Assuming you set up a SysV-style init script, you can
simply launch it as:

# /etc/rc.d/init.d/named start

Make sure you kill any old versions of BIND still running before doing this.

If you take a look at your logs, you should find the initialisation messages
that BIND spits out when it loads. (If not, there's a problem with your
logging configuration that you need to fix.) Amongst those
messages, BIND should tell you that it chrooted successfully, and that it is
running as the user and group named. If not, you have a problem.