Naming and Directory Services (DNS, NIS, and LDAP)

EXAMPLE 3–2 Sample named.conf File Entry for rndc(Continued)key "rndc-key" {algorithm hmac-md5;secret "qPWZ3Ndl81aBRY9AmJhVtU==";};Differences in the Control ChannelsBoth the ndc and the rndc utilities use a control channel to send commands to andretrieve information from a name server. However, there are differences between theutilities.■■■In BIND 8, ndc can use AF_UNIX domain sockets (UNIX control channel) orTCP/IP sockets (inet control channel). By default, ndc does not need any supportin /etc/named.conf, because BIND 8 servers use a UNIX domain socket with apath (/var/run/ndc.d/ndc) compiled into in.named.For BIND 9, however, rndc only uses an authenticated TCP/IP inet controlchannel and so is not backward compatible with BIND 8. There is no UNIX domainsocket support for control channels in BIND 9 servers.When using rndc, you need to specify a ’key’ clause to communicate with thename server. It is mandatory that the BIND 9 server and the rndc client share thesame key (defined both in /etc/named.conf and /etc/rndc.conf). Using theBIND 8 controls entry in BIND 9 will result in an error message.Some command options have changed from the ndc to the rndc implementation.This includes the -c option, which has a different syntax in BIND 9. Therefore, tospecify the control channel in BIND 9, use rndc -s -p .Commands of BIND 9 rndcThe following list describes the rndc commands.reloadreload zone [class [view]]refresh zone [class [view]]reconfigstatsquerylogdumpdbstopReload configuration file and zonesReload a single zoneSchedule immediate maintenance for a zoneReload configuration file and new zones onlyWrite server statistics to the statistics fileToggle query loggingDump cache(s) to the dump file (named_dump.db)Save pending updates to master files and stop theserverChapter 3 • DNS Setup and Administration (Reference) 51