| Where allowed to run: All environments (*ALL) Threadsafe: No |
Parameters Examples Error messages |
The Run RNDC Command (RUNRNDCCMD) command, or its alias RNDC, starts the Remote Name Daemon Control utility. This command allows you to control a Domain Name System (DNS) running on your local system.
Restrictions:
| Top |
| Keyword | Description | Choices | Notes |
|---|---|---|---|
| RNDCCMD | RNDC command | Character value | Required, Positional 1 |
| DMNNAMSVR | Domain name server | Character value, *DFT | Optional, Positional 2 |
| PORT | Domain name server port | 1-65535, 953 | Optional, Positional 3 |
| RNDCCFGF | RNDC configuration file | Path name, *DFT | Optional |
| SRCADR | Source address | Character value, *DFT, *ANY4, *LOOPBACK4, *ANY6, *LOOPBACK6 | Optional |
| KEYFILE | Key file | Path name, *DFT | Optional |
| KEYNAME | Key name | Character value, *DFT | Optional |
| DEBUG | Show debug information | *NO, *YES | Optional |
| TOSTMF | Output file | Path name, *STDOUT | Optional |
| Top |
Specifies the control command to be sent to the DNS server.
This is a required parameter.
reload
Reload configuration file and zones
reload zone [class [view]]
Reload a single zone
refresh zone [class [view]]
Schedule immediate maintenance for a zone
retransfer zone [class [view]]
Re-transfer a single zone without checking
serial number
freeze zone [class [view]]
Suspend updates to a dynamic zone
thaw zone [class [view]]
Enable updates to a frozen dynamic zone and
reload it
reconfig
Reload configuration file and new zones only
stats
Write server statistics to the statistics file
querylog
Toggle query logging
dumpdb [-all|-cache|-zones] [view ...]
Dump cache(s) to the dump file (named_dump.db)
stop
Save pending updates to master files and stop
the server
stop -p
Save pending updates to master files and stop
the server reporting process id
halt
Stop the server without saving pending updates
halt -p
Stop the server without saving pending updates
reporting process id
trace
Increment debugging level by one
trace level
Change the debugging level
notrace
Set debugging level to 0
flush
Flushes all of the servers caches
flush [view]
Flushes the servers cache for a view
flushname name [view]
Flush the given name from the servers cache(s)
status
Display status of the server
recursing
Dump the queries that are currently recursing
(named.recursing)
| Top |
Specifies the name or the IP address of the DNS server that RNDC will use as its current server for the query session. You can specify any DNS server to which your TCP/IP network has access.
Note: RNDC sends information to DNS servers and it needs an active DNS server to send its commands. If you do not specify a DNS server with DMNNAMSVR when you start the tool, it will attempt to use the default server, port and key defined in the rndc.conf file. This is usually the loopback interface 127.0.0.1 and port 953.
| Top |
Specifies the default server port to use.
| Top |
Specifies the RNDC configuration file to be used for this session. This file contains both access key and option statements that define the default server and the access key for that server. It is possible to use RNDC to control DNS servers located on other systems if this configuration file contains the access key and server statements that apply to the remote servers.
| Top |
Specifies the source address for the connection to the server.
| Top |
Specifies the access key file to use for this session. The key in this file will be used to authenticate commands sent to the server.
| Top |
Specifies the access key name to be used for this session. This key name must be known by the server that is being used for this session. If no key name is specified, RNDC will use the defaults from the /QIBM/UserData/OS400/DNS/_DYN/rndc.conf file.
The DNS server being queried needs to include this key and algorithm in its named.conf configuration file in order to allow RNDC clients with this key.
| Top |
Specifies whether or not to turn debugging mode on. More information is displayed about the packet sent to the server and the resulting answer when debugging mode is on.
| Top |
Specifies the name of a stream file where all command output is written.
| Top |
Example 1: Reload All DNS Server Configuration and Static Zones
RUNRNDCCMD RNDCCMD('reload')
This command illustrates a simple reload of any changes to a DNS server configuration and any static zones.
The output from this type of query might look like this:
server reload successful
Similarly, if your RNDC key from the rndc.conf file is not valid, the output from this type of query might look like this:
rndc: connection to remote host closed This may indicate that * the remote server is using an older version of the command protocol, * this host is not authorized to connect, * the clocks are not syncronized, or * the key is invalid.
Example 2: Reload a Single Zone
RUNRNDCCMD RNDCCMD('reload i5os.ibm.com')
This command illustrates a simple reload of a single static zone called 'i5os.ibm.com'.
The output from this type of query might look like this:
zone reload up-to-date
If the zone is not a static zone, the output from this type of query might look like this:
rndc: 'reload i5os.ibm.com' failed: dynamic zone
Example 3: Dumping the Cache
RUNRNDCCMD RNDCCMD('dumpdb -cache')
This command illustrates how to dump the active cache on the server. The output from this type of query will be empty, because it goes to file named_dump.db in the server directory, i.e., for server NS the file would be /QIBM/UserData/OS400/DNS/NS/named_dump.db.
| Top |
*ESCAPE Messages
| Top |