rndc

Linux 4gvps.4gvps.com 3.10.0-1127.18.2.vz7.163.46 #1 SMP Fri Nov 20 21:47:55 MSK 2020 x86_64
SOFT : Apache PHP : 7.4.33
/usr/share/doc/bind-9.11.4/

38.135.39.45

[ NAME ]	[ SIZE ]	[ PERM ]	[ DATE ]	[ ACT ]
+FILE +DIR
sample	dir	drwxr-xr-x	2025-03-28 11:31	R D
Bv9ARM.ch01.html	26.113 KB	-rw-r--r--	2018-09-04 04:04	R E G D
Bv9ARM.ch02.html	7.18 KB	-rw-r--r--	2018-09-04 04:04	R E G D
Bv9ARM.ch03.html	30.385 KB	-rw-r--r--	2018-09-04 04:04	R E G D
Bv9ARM.ch04.html	129.648 KB	-rw-r--r--	2018-09-04 04:04	R E G D
Bv9ARM.ch05.html	6.288 KB	-rw-r--r--	2018-09-04 04:04	R E G D
Bv9ARM.ch06.html	684.152 KB	-rw-r--r--	2018-09-04 04:04	R E G D
Bv9ARM.ch07.html	19.563 KB	-rw-r--r--	2018-09-04 04:04	R E G D
Bv9ARM.ch08.html	6.315 KB	-rw-r--r--	2018-09-04 04:04	R E G D
Bv9ARM.ch09.html	10.269 KB	-rw-r--r--	2018-09-04 04:04	R E G D
Bv9ARM.ch10.html	6.919 KB	-rw-r--r--	2018-09-04 04:04	R E G D
Bv9ARM.ch11.html	53.243 KB	-rw-r--r--	2018-09-04 04:04	R E G D
Bv9ARM.ch12.html	20.447 KB	-rw-r--r--	2018-09-04 04:04	R E G D
Bv9ARM.ch13.html	9.875 KB	-rw-r--r--	2018-09-04 04:04	R E G D
Bv9ARM.html	29.705 KB	-rw-r--r--	2018-09-04 04:04	R E G D
Bv9ARM.pdf	1.24 MB	-rw-r--r--	2018-09-04 04:04	R E G D
CHANGES	528.756 KB	-rw-r--r--	2018-09-04 04:04	R E G D
README	22.464 KB	-rw-r--r--	2018-09-04 04:04	R E G D
isc-logo.pdf	281.241 KB	-rw-r--r--	2018-09-04 04:04	R E G D
man.arpaname.html	3.008 KB	-rw-r--r--	2018-09-04 04:04	R E G D
man.ddns-confgen.html	9.493 KB	-rw-r--r--	2018-09-04 04:04	R E G D
man.delv.html	23.869 KB	-rw-r--r--	2018-09-04 04:04	R E G D
man.dig.html	40.626 KB	-rw-r--r--	2018-09-04 04:04	R E G D
man.dnssec-checkds.html	5.354 KB	-rw-r--r--	2018-09-04 04:04	R E G D
man.dnssec-coverage.html	11.349 KB	-rw-r--r--	2018-09-04 04:04	R E G D
man.dnssec-dsfromkey.html	9.684 KB	-rw-r--r--	2018-09-04 04:04	R E G D
man.dnssec-importkey.html	9.577 KB	-rw-r--r--	2018-09-04 04:04	R E G D
man.dnssec-keyfromlabel.html	19.122 KB	-rw-r--r--	2018-09-04 04:04	R E G D
man.dnssec-keygen.html	22.314 KB	-rw-r--r--	2018-09-04 04:04	R E G D
man.dnssec-keymgr.html	15.15 KB	-rw-r--r--	2018-09-04 04:04	R E G D
man.dnssec-revoke.html	5.618 KB	-rw-r--r--	2018-09-04 04:04	R E G D
man.dnssec-settime.html	14.555 KB	-rw-r--r--	2018-09-04 04:04	R E G D
man.dnssec-signzone.html	30.69 KB	-rw-r--r--	2018-09-04 04:04	R E G D
man.dnssec-verify.html	7.431 KB	-rw-r--r--	2018-09-04 04:04	R E G D
man.dnstap-read.html	4.391 KB	-rw-r--r--	2018-09-04 04:04	R E G D
man.genrandom.html	4.135 KB	-rw-r--r--	2018-09-04 04:04	R E G D
man.host.html	12.742 KB	-rw-r--r--	2018-09-04 04:04	R E G D
man.isc-hmac-fixup.html	4.601 KB	-rw-r--r--	2018-09-04 04:04	R E G D
man.lwresd.html	12.447 KB	-rw-r--r--	2018-09-04 04:04	R E G D
man.mdig.html	23.176 KB	-rw-r--r--	2018-09-04 04:04	R E G D
man.named-checkconf.html	6.769 KB	-rw-r--r--	2018-09-04 04:04	R E G D
man.named-checkzone.html	20.205 KB	-rw-r--r--	2018-09-04 04:04	R E G D
man.named-journalprint.html	4.195 KB	-rw-r--r--	2018-09-04 04:04	R E G D
man.named-nzd2nzf.html	3.859 KB	-rw-r--r--	2018-09-04 04:04	R E G D
man.named-rrchecker.html	4.21 KB	-rw-r--r--	2018-09-04 04:04	R E G D
man.named.conf.html	73.419 KB	-rw-r--r--	2018-09-04 04:04	R E G D
man.named.html	19.072 KB	-rw-r--r--	2018-09-04 04:04	R E G D
man.nsec3hash.html	4.175 KB	-rw-r--r--	2018-09-04 04:04	R E G D
man.nslookup.html	14.487 KB	-rw-r--r--	2018-09-04 04:04	R E G D
man.nsupdate.html	28.107 KB	-rw-r--r--	2018-09-04 04:04	R E G D
man.pkcs11-destroy.html	5.569 KB	-rw-r--r--	2018-09-04 04:04	R E G D
man.pkcs11-keygen.html	7.133 KB	-rw-r--r--	2018-09-04 04:04	R E G D
man.pkcs11-list.html	5.463 KB	-rw-r--r--	2018-09-04 04:04	R E G D
man.pkcs11-tokens.html	3.733 KB	-rw-r--r--	2018-09-04 04:04	R E G D
man.rndc-confgen.html	11.477 KB	-rw-r--r--	2018-09-04 04:04	R E G D
man.rndc.conf.html	10.174 KB	-rw-r--r--	2018-09-04 04:04	R E G D
man.rndc.html	39.894 KB	-rw-r--r--	2018-09-04 04:04	R E G D
named.conf.default	1.764 KB	-rw-r--r--	2025-03-28 11:31	R E G D
notes.html	7.309 KB	-rw-r--r--	2018-09-04 04:04	R E G D
notes.pdf	50.958 KB	-rw-r--r--	2018-09-04 04:04	R E G D
REQUEST EXIT

rndc
Prev�	Manual pages	�Next

rndc

Prev�

Manual pages

�Next

DESCRIPTION

rndc controls the operation of a name server. It supersedes the ndc utility that was provided in old BIND releases. If rndc is invoked with no command line options or arguments, it prints a short summary of the supported commands and the available options and their arguments.

rndc communicates with the name server over a TCP connection, sending commands authenticated with digital signatures. In the current versions of rndc and named, the only supported authentication algorithms are HMAC-MD5 (for compatibility), HMAC-SHA1, HMAC-SHA224, HMAC-SHA256 (default), HMAC-SHA384 and HMAC-SHA512. They use a shared secret on each end of the connection. This provides TSIG-style authentication for the command request and the name server's response. All commands sent over the channel must be signed by a key_id known to the server.

rndc reads a configuration file to determine how to contact the name server and decide what algorithm and key it should use.

OPTIONS

-b source-address: Use source-address as the source address for the connection to the server. Multiple instances are permitted to allow setting of both the IPv4 and IPv6 source addresses.
-c config-file: Use config-file as the configuration file instead of the default, /etc/rndc.conf.
-k key-file: Use key-file as the key file instead of the default, /etc/rndc.key. The key in /etc/rndc.key will be used to authenticate commands sent to the server if the config-file does not exist.
-s server: server is the name or address of the server which matches a server statement in the configuration file for rndc. If no server is supplied on the command line, the host named by the default-server clause in the options statement of the rndc configuration file will be used.
-p port: Send commands to TCP port port instead of BIND 9's default control channel port, 953.
-q: Quiet mode: Message text returned by the server will not be printed except when there is an error.
-r: Instructs rndc to print the result code returned by named after executing the requested command (e.g., ISC_R_SUCCESS, ISC_R_FAILURE, etc).
-V: Enable verbose logging.
-y key_id: Use the key key_id from the configuration file. key_id must be known by named with the same algorithm and secret string in order for control message validation to succeed. If no key_id is specified, rndc will first look for a key clause in the server statement of the server being used, or if no server statement is present for that host, then the default-key clause of the options statement. Note that the configuration file contains shared secrets which are used to send authenticated control commands to name servers. It should therefore not have general read or write access.

COMMANDS

A list of commands supported by rndc can be seen by running rndc without arguments.

Currently supported commands are:

addzone zone [class [view]] configuration

Add a zone while the server is running. This command requires the allow-new-zones option to be set to yes. The configuration string specified on the command line is the zone configuration text that would ordinarily be placed in named.conf.

The configuration is saved in a file called name.nzf, where name is the name of the view, or if it contains characters that are incompatible with use as a file name, a cryptographic hash generated from the name of the view. When named is restarted, the file will be loaded into the view configuration, so that zones that were added can persist after a restart.

This sample addzone command would add the zone example.com to the default view:

$ rndc addzone example.com '{ type master; file "example.com.db"; };'

(Note the brackets and semi-colon around the zone configuration text.)

See also rndc delzone and rndc modzone.

delzone [-clean] zone [class [view]]

Delete a zone while the server is running.

If the -clean argument is specified, the zone's master file (and journal file, if any) will be deleted along with the zone. Without the -clean option, zone files must be cleaned up by hand. (If the zone is of type "slave" or "stub", the files needing to be cleaned up will be reported in the output of the rndc delzone command.)

If the zone was originally added via rndc addzone, then it will be removed permanently. However, if it was originally configured in named.conf, then that original configuration is still in place; when the server is restarted or reconfigured, the zone will come back. To remove it permanently, it must also be removed from named.conf

See also rndc addzone and rndc modzone.

dnstap ( -reopen | -roll [number] )

Close and re-open DNSTAP output files. rndc dnstap -reopen allows the output file to be renamed externally, so that named can truncate and re-open it. rndc dnstap -roll causes the output file to be rolled automatically, similar to log files; the most recent output file has ".0" appended to its name; the previous most recent output file is moved to ".1", and so on. If number is specified, then the number of backup log files is limited to that number.

Dump the server's caches (default) and/or zones to the dump file for the specified views. If no view is specified, all views are dumped. (See the dump-file option in the BIND 9 Administrator Reference Manual.)

flush

Flushes the server's cache.

flushname name [view]

Flushes the given name from the view's DNS cache and, if applicable, from the view's nameserver address database, bad server cache and SERVFAIL cache.

flushtree name [view]

Flushes the given name, and all of its subdomains, from the view's DNS cache, address database, bad server cache, and SERVFAIL cache.

freeze [zone [class [view]]]

Suspend updates to a dynamic zone. If no zone is specified, then all zones are suspended. This allows manual edits to be made to a zone normally updated by dynamic update. It also causes changes in the journal file to be synced into the master file. All dynamic update attempts will be refused while the zone is frozen.

Prev�	Up	�Next
nsupdate�	Home	�`rndc.conf`

Name

Synopsis

DESCRIPTION

OPTIONS

COMMANDS

LIMITATIONS

SEE ALSO