47 lines
1.6 KiB
HTML
47 lines
1.6 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
|
<HTML>
|
|
<HEAD>
|
|
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
|
|
<TITLE>Chroot-BIND8 HOWTO: The End</TITLE>
|
|
<LINK HREF="Chroot-BIND8-HOWTO-6.html" REL=next>
|
|
<LINK HREF="Chroot-BIND8-HOWTO-4.html" REL=previous>
|
|
<LINK HREF="Chroot-BIND8-HOWTO.html#toc5" REL=contents>
|
|
</HEAD>
|
|
<BODY>
|
|
<A HREF="Chroot-BIND8-HOWTO-6.html">Next</A>
|
|
<A HREF="Chroot-BIND8-HOWTO-4.html">Previous</A>
|
|
<A HREF="Chroot-BIND8-HOWTO.html#toc5">Contents</A>
|
|
<HR>
|
|
<H2><A NAME="s5">5. The End</A></H2>
|
|
|
|
<H2><A NAME="ss5.1">5.1 Launching BIND</A>
|
|
</H2>
|
|
|
|
<P>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:
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
# /etc/rc.d/init.d/named start
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
|
|
Make sure you kill any old versions of BIND still running before doing this.
|
|
<P>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
|
|
<A HREF="Chroot-BIND8-HOWTO-2.html#logging">logging configuration</A> 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 <CODE>named</CODE>. If not, you have a problem.
|
|
<P>
|
|
<H2><A NAME="ss5.2">5.2 That's It!</A>
|
|
</H2>
|
|
|
|
<P>You can go take a nap now ;-).
|
|
<P>
|
|
<HR>
|
|
<A HREF="Chroot-BIND8-HOWTO-6.html">Next</A>
|
|
<A HREF="Chroot-BIND8-HOWTO-4.html">Previous</A>
|
|
<A HREF="Chroot-BIND8-HOWTO.html#toc5">Contents</A>
|
|
</BODY>
|
|
</HTML>
|