Commit c26b4224 authored by Jan Včelák's avatar Jan Včelák 🚀
Browse files

doc: not Bind but BIND

parent c8d99b85
......@@ -174,7 +174,7 @@ Zone name/server guessing, if the zone name/server is not specified.
.sp
Empty line doesn\(aqt send the update.
.sp
Bind\-like key format (\fBddns\-confgen\fP output) is not supported.
BIND\-like key format (\fBddns\-confgen\fP output) is not supported.
.UNINDENT
.UNINDENT
.SH EXAMPLES
......
......@@ -148,7 +148,7 @@ Differences with regard to ISC nsupdate:
Empty line doesn't send the update.
Bind-like key format (:program:`ddns-confgen` output) is not supported.
BIND-like key format (:program:`ddns-confgen` output) is not supported.
Examples
--------
......
......@@ -15,12 +15,12 @@ Knot DNS for BIND users
Automatic DNSSEC signing
------------------------
Migrating automatically signed zones from Bind to Knot DNS is very
Migrating automatically signed zones from BIND to Knot DNS is very
easy due to the fact that Knot DNS is able to use DNSSEC keys
generated by Bind.
generated by BIND.
1. To obtain current content of the zone which is being migrated,
request Bind to flush the zone into the zone file: ``rndc flush
request BIND to flush the zone into the zone file: ``rndc flush
example.com``.
*Note:* If dynamic updates (DDNS) are enabled for the given zone, you
......@@ -33,7 +33,7 @@ generated by Bind.
3. We recommend to store DNSSEC keys for each zone in a separate
directory. For this purpose, create a directory
``example.com.keys`` in the zones storage directory. Then copy all
DNSSEC keys (``*.key`` and ``*.private``) from Bind key directory
DNSSEC keys (``*.key`` and ``*.private``) from BIND key directory
(configured as ``key-directory``) into the newly created one.
4. Add the zone into the Knot DNS configuration file. Zone
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment