Files
bind9/doc/design/keydone
Matthijs Mekking 2af05beafa Replace "master/slave" terms in code
Replace some "master/slave" terminology in the code with the preferred
"primary/secondary" keywords. This also changes user output such as
log messages, and fixes a typo ("seconary") in cfg_test.c.

There are still some references to "master" and "slave" for various
reasons:

- The old syntax can still be used as a synonym.
- The master syntax is kept when it refers to master files and formats.
- This commit replaces mainly keywords that are local. If "master" or
  "slave" is used in for example a structure that is all over the
  place, it is considered out of scope for the moment.
2021-10-12 13:11:13 -07:00

33 lines
1.1 KiB
Plaintext

Copyright (C) Internet Systems Consortium, Inc. ("ISC")
See COPYRIGHT in the source root or https://isc.org/copyright.html for terms.
rndc keydone <rdata> zone [class [view]]
e.g.
rndc keydone 0549E00001 example
Last 4 characters need to be 0001 (00=no flags, 01=done)
First 2 characters (algorithm) not 00 (algorithm 0 which
is reserved, 00 => NSEC3PARAMETERS are encoded in the record)
All hexadecimal case insensitive. length 10.
Err: DNS_R_SYNTAX
The control code will select the zone based on 'zone [class
[view]]'.
Err: DNS_R_NOTFOUND
zone must be a primary (signed inline == primary) or normal
dynamic zone.
Err: DNS_R_NOTPRIMARY
dns_zone_<something>(zone, text) which will send a event
to the zone so that the deletion gets run in the zone's
task. The event handler will delete the record, update the
SOA and write out the journal.
Err: ISC_R_NOMEMORY
'zone' can refer to a normal dynamic master zone or a inline
zone.