mir/bind
2
0
Fork 0
mirror of https://gitlab.isc.org/isc-projects/bind9 synced 2025-08-30 14:07:59 +00:00
Code Issues Releases Wiki Activity

fix a few typos in doc

Browse Source
This commit is contained in:
Jeremy C. Reed
2016-05-27 15:22:54 -04:00
parent 7898bf1fbc
commit ecf8e705e6
1 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
doc/arm/catz.xml
View File

@@ -23,8 +23,8 @@
When a catalog zone is loaded or transferred to a slave server When a catalog zone is loaded or transferred to a slave server
which supports this functionality, the slave server will create which supports this functionality, the slave server will create
the member zones automatically. When the catalog zone is updated the member zones automatically. When the catalog zone is updated
is updated (for example, to add or delete member zones, or change (for example, to add or delete member zones, or change
their configuration aprameters) those changes are immediately put their configuration parameters) those changes are immediately put
into effect. Because the catalog zone is a normal DNS zone, these into effect. Because the catalog zone is a normal DNS zone, these
configuration changes can be propagated using the standard AXFR/IXFR configuration changes can be propagated using the standard AXFR/IXFR
zone transfer mechanism. zone transfer mechanism.
@@ -95,7 +95,7 @@
catalog cone is propagated to the slave server using the normal AXFR/IXFR catalog cone is propagated to the slave server using the normal AXFR/IXFR
transfer mechanism. The slave server, on processing the update, will transfer mechanism. The slave server, on processing the update, will
notice that the member zone has been removed. It will stop serving the notice that the member zone has been removed. It will stop serving the
zone and remove it froms its list of configured zones. (Removing the zone and remove it from its list of configured zones. (Removing the
member zone from the master server has to be done in the normal way, member zone from the master server has to be done in the normal way,
by editing the configuration file or running by editing the configuration file or running
<command>rndc delzone</command>.) <command>rndc delzone</command>.)
@@ -121,7 +121,7 @@ catalog-zones {
</para> </para>
<para> <para>
The <option>default-masters</option> option defines the default masters The <option>default-masters</option> option defines the default masters
for member zones listed in a catalog zone. This can be overriden by for member zones listed in a catalog zone. This can be overridden by
options within a catalog zone. If no such options are included, then options within a catalog zone. If no such options are included, then
member zones will transfer their contents from the servers listed in member zones will transfer their contents from the servers listed in
this option. this option.
@@ -178,7 +178,7 @@ version.catalog.example. IN TXT "1"
all member zones, overriding the settings for the catalog zone all member zones, overriding the settings for the catalog zone
in the configuration file. Currently only the "masters" option in the configuration file. Currently only the "masters" option
is supported: is supported:
<!-- TODO masters IN MX (with TSIG), allow-query, allow-tranfer --> <!-- TODO masters IN MX (with TSIG), allow-query, allow-transfer -->
</para> </para>
<screen> <screen>
masters.catalog.example IN A 192.0.2.1 masters.catalog.example IN A 192.0.2.1