6b6ac9438f
package does have BXA export approval, but the licensing strings on the dnssafe code are a bit unpleasant. The crypto is easy to restore and bind will run without it - just without full dnssec support. Obtained from: The Internet Software Consortium (www.isc.org)
58 lines
1.4 KiB
HTML
58 lines
1.4 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
|
<HTML>
|
|
<HEAD>
|
|
<TITLE>BIND include Statement</TITLE>
|
|
</HEAD>
|
|
|
|
<BODY>
|
|
<H2>BIND Configuration File Guide--<CODE>include</CODE> Statement</H2>
|
|
|
|
<HR>
|
|
|
|
<A NAME="Syntax"><H3>Syntax</H3></A>
|
|
|
|
<PRE>
|
|
include <VAR><A HREF="docdef.html">path_name</A></VAR>;
|
|
</PRE>
|
|
|
|
<HR>
|
|
|
|
<A Name="#Usage"><H3>Definition and Usage</H3></A>
|
|
|
|
<P>The <CODE>include</CODE> statement inserts the specified file at
|
|
the point that the <CODE>include</CODE> statement is encountered. It
|
|
cannot be used within another statement, though, so a line such as
|
|
<PRE>
|
|
acl internal_hosts { include "internal_hosts.acl"; };
|
|
</PRE>
|
|
is not allowed.</P>
|
|
|
|
<P>Use <CODE>include</CODE> to break the configuration up into
|
|
easily-managed chunks. For example:
|
|
|
|
<PRE>
|
|
include "/etc/security/keys.bind";
|
|
include "/etc/acls.bind";
|
|
</PRE>
|
|
|
|
<P>could be used at the top of a BIND configuration file in order to
|
|
include any ACL or key information.</P>
|
|
|
|
<P>Be careful not to type
|
|
"<CODE>#include</CODE>", like you would in a C
|
|
program, because "<CODE>#</CODE>" is used to start a
|
|
comment.</P>
|
|
|
|
<HR>
|
|
|
|
<CENTER><P>[ <A HREF="config.html">BIND Config. File</A>
|
|
| <A HREF="http://www.isc.org/products/BIND/">BIND Home</A>
|
|
| <A HREF="http://www.isc.org/">ISC</A> ]</P></CENTER>
|
|
|
|
<HR>
|
|
<ADDRESS>
|
|
Last Updated: $Id: include.html,v 1.7 1999/09/15 20:28:01 cyarnell Exp $
|
|
</ADDRESS>
|
|
</BODY>
|
|
</HTML>
|