JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP)     Oracle Solaris 11 Express 11/10
search filter icon
search icon

Document Information


Part I About Naming and Directory Services

1.  Naming and Directory Services (Overview)

2.  The Name Service Switch (Overview)

Part II DNS Setup and Administration

3.  DNS Setup and Administration (Reference)

Related Materials

Migrating From BIND 8 to BIND 9

DNS and the Service Management Facility

Implementing rndc

The rndc.conf Configuration File

Differences in the Control Channels

Commands of BIND 9 rndc

BIND 9 Commands, Files, Tools, and Options

BIND 9 Tools and Configuration Files

Comparison of BIND 8 and BIND 9 Commands and Files

Descriptions of Command and Option Changes

The named.conf Options

Statements in BIND 9

The Controls Statement

The Zone Statement

The ACL Statement

The Key Statement

The Trusted-Keys Statement

The Server Statement

The Include Statement

Summary of the named.conf Options

Multicast DNS and Service Discovery

Multicast DNS

Service Discovery

Administering mDNS

mDNS Deployment

Enable mDNS

Edit nsswitch.conf

Review Errors or Messages

mDNS and dns-sd Tool

Part III NIS Setup and Administration

4.  Network Information Service (NIS) (Overview)

5.  Setting Up and Configuring NIS Service

6.  Administering NIS (Tasks)

7.  NIS Troubleshooting

Part IV LDAP Naming Services Setup and Administration

8.  Introduction to LDAP Naming Services (Overview/Reference)

9.  LDAP Basic Components and Concepts (Overview)

10.  Planning Requirements for LDAP Naming Services (Tasks)

11.  Setting Up Sun Java System Directory Server With LDAP Clients (Tasks)

12.  Setting Up LDAP Clients (Tasks)

13.  LDAP Troubleshooting (Reference)

14.  LDAP General Reference (Reference)

15.  Transitioning From NIS to LDAP (Overview/Tasks)

Part V Active Directory Naming Service

16.  Setting Up Oracle Solaris Active Directory Clients



Implementing rndc

The BIND 8 ndc and BIND 9 rndc name server control tools are not backward compatible. rndc can not talk to the BIND 8 name server and ndc can not talk to the BIND 9 name server. Features, options, default modes of operation, and configuration file requirements have changed. Therefore, using ndc on a BIND 9 server could result in loss of functionality or insecure operation. See the rndc(1M) man page for more information.

The rndc.conf Configuration File

The most significant difference between ndc in BIND 8 and rndc in BIND 9 is that rndc needs its own configuration file, rndc.conf. This file can be generated by rndc-confgen commands. The rndc.conf file specifies which server controls and what algorithm the server should use.

Example 3-1 Sample rndc.conf File

options {
             default-server localhost;
             default-key "rndc-key";

     key "rndc-key" {
             algorithm hmac-md5;
             secret "qPWZ3Ndl81aBRY9AmJhVtU==";

Example 3-2 Sample named.conf File Entry for rndc

controls {
             inet * allow { any; } keys { "rndc-key"; };

     key "rndc-key" {
             algorithm hmac-md5;
             secret "qPWZ3Ndl81aBRY9AmJhVtU==";

Differences in the Control Channels

Both the ndc and the rndc utilities use a control channel to send commands to and retrieve information from a name server. However, there are differences between the utilities.

Commands of BIND 9 rndc

The following list describes the rndc commands.


Reload configuration file and zones

reload zone [class [view]]

Reload a single zone

refresh zone [class [view]]

Schedule immediate maintenance for a zone


Reload configuration file and new zones only


Write server statistics to the statistics file


Toggle query logging


Dump cache(s) to the dump file (named_dump.db)


Save pending updates to master files and stop the server


Stop the server without saving pending updates


Increment debugging level by one

trace level

Change the debugging level


Set debugging level to 0


Flushes all of the server's caches

flush [view]

Flushes the server's cache for a view


Display status of the server


Restart the server (not yet implemented)