Operation Manual

the "." at the end. Appending the zone to this (without the .in-addr.arpa)
results in the complete IP address in reverse order.
Normally, zone transfers between different versions of BIND should be possible without
any problems.
25.7 Dynamic Update of Zone Data
The term dynamic update refers to operations by which entries in the zone les of a
master server are added, changed, or deleted. This mechanism is described in RFC 2136.
Dynamic update is congured individually for each zone entry by adding an optional
allow-update or update-policy rule. Zones to update dynamically should not
be edited by hand.
Transmit the entries to update to the server with the command nsupdate. For the
exact syntax of this command, check the manual page for nsupdate (man 8 nsupdate).
For security reasons, any such update should be performed using TSIG keys as described
in Section 25.8, “Secure Transactions” (page 443).
25.8 Secure Transactions
Secure transactions can be made with the help of transaction signatures (TSIGs) based
on shared secret keys (also called TSIG keys). This section describes how to generate
and use such keys.
Secure transactions are needed for communication between different servers and for
the dynamic update of zone data. Making the access control dependent on keys is much
more secure than merely relying on IP addresses.
Generate a TSIG key with the following command (for details, see
man dnssec-keygen):
dnssec-keygen -a hmac-md5 -b 128 -n HOST host1-host2
This creates two les with names similar to these:
Khost1-host2.+157+34265.private Khost1-host2.+157+34265.key
The Domain Name System 443