|
@@ -449,7 +449,8 @@ var/
|
|
|
|
|
|
<listitem>
|
|
|
<para>Load desired zone file(s), for example:
|
|
|
- <screen>$ <userinput>b10-loadzone <replaceable>your.zone.example.org</replaceable></userinput></screen>
|
|
|
+
|
|
|
+ <screen>$ <userinput>b10-loadzone <replaceable>-c '{"database_file": "/usr/local/var/bind10/zone.sqlite3"}'</replaceable> <replaceable>your.zone.example.org</replaceable> <replaceable>your.zone.file</replaceable></userinput></screen>
|
|
|
</para>
|
|
|
</listitem>
|
|
|
|
|
@@ -2636,19 +2637,10 @@ can use various data source backends.
|
|
|
|
|
|
</para>
|
|
|
|
|
|
- <para>
|
|
|
- The <option>-o</option> argument may be used to define the
|
|
|
- default origin for loaded zone file records.
|
|
|
- </para>
|
|
|
-
|
|
|
<note>
|
|
|
<para>
|
|
|
In the current release, only the SQLite3 back
|
|
|
end is used by <command>b10-loadzone</command>.
|
|
|
- By default, it stores the zone data in
|
|
|
- <filename>/usr/local/var/bind10-devel/zone.sqlite3</filename>
|
|
|
- unless the <option>-d</option> switch is used to set the
|
|
|
- database filename.
|
|
|
Multiple zones are stored in a single SQLite3 zone database.
|
|
|
</para>
|
|
|
</note>
|