Subtitles of the Movie

Now you can move on to the RNDC configuration; open a file called /etc/rndc.conf in your text editor. Enter a key statement, identical to the one in the named.conf file. The key name should be the same; you can just copy and paste this statement out of the named.conf file if you want. Next, start an options statement, by typing options followed by an open brace. On the next line, enter – default -server 127.0.0.1; - this defines the default server to which RNDC will connect. On the next line, specify default, dash key, followed by the key name, as defined in the key statement in quotes, followed by a semicolon. Now close the options statement, with a close brace and a semicolon, save this file and exit. RNDC should now be functional to control the local server; you may want to put /user/local/sbin in your path to make running RNDC easier. Type RNDC, with no options, to see a list of available commands. The most common use of RNDC is reload, which reloads the configuration and all zone files in the memory, updating the server with any changes made. You can also use RNDC reload, followed by a zone name, to reload only that specific zone, which is far faster when you have a lot of zones. This won’t update any changes to the named.conf file though, only to the specified zone file; using the RNDC reconfig command reloads the named.conf file, and only in the new zone files. Existing zone files aren't reloaded even if they've been changed. Again this is faster when you have a lot of zones; the remaining RNDC commands are used primarily for advanced trouble shooting. Be careful if you decide to experiment with them, enabling query logging or tracing on a busy DNS server can overwhelm the system quickly.