|
|
BIND 9 ---> no /etc/named.conf file after installation
|
|
bindsetup(8) System Manager's Manual bindsetup(8) Name bindsetup - set up the Berkeley Internet Name Domain (BIND)/Hesiod service Syntax /usr/etc/bindsetup [ -c [ -d directory ] -b binddomain name1,IP1 name2,IP2 ... ] Description The command sets up the Berkeley Internet Name Domain (BIND)/Hesiod service on your system and places and resolution under BIND/Hesiod con- trol. You can use this command to set up your system as a primary, secondary, slave, or caching server, or as a client. In order to run BIND/Hesiod, your system's host name must include the BIND domain name. The BIND host name consists of the local host name plus the BIND domain name, separated by periods. For example, the BIND host name for a system whose local host name is and whose BIND domain name is is The command edits the and files and changes the local host name to the BIND host name, if it is not there already. If the command changes your system's host name, you should reboot the system to be sure that the change is propagated throughout the sys- tem. Before you run , your system must be established on a local area network. In addition, you must know the BIND domain name for your local area network, and whether your system will be a primary, secondary, slave, or caching server, or a client. The command asks if you want to run a Kerberos authentication server. You must already have set up Kerberos to do do. For more informa- tion, see the Guide to Kerberos. You should run the command as superuser and with the system in multiuser mode. If you use the option with the respective arguments, the command sets up your system as a BIND/Hesiod client non-interactively. If you run the command with no arguments, a menu is displayed giving you a choice of responses. You are then prompted for further informa- tion. Before exits, it lists the files that have been updated. Once BIND/Hesiod is installed on a machine, it cannot be used until the file is modified to contain BIND entries on the desired database lines. The command reminds a user to run or edit the file manually. Options -c Sets up your system as a BIND/Hesiod client according to the following arguments you supply on the command line: -d directory This option and argument are required if you are setting up a diskless client from the diskless server. The directory is the full path name of the root directory for your system (a diskless client) on the diskless server. The following is an example of a root directory for a diskless client named /dlclient0/orange.root -b binddomain This is the name of the BIND domain on which your system will be a BIND client. For example, is a sample BIND domain name. name,IP This is the host name and the IP address of the BIND server on the domain, for example You can specify one or more BIND server by listing more name,IP arguments, each separated by a space. Files List of locally maintained host names and IP addresses Startup commands pertinent to a specific system Database name with the selected naming services Hesiod configuration file List of Kerberos servers Default BIND Files: BIND server data file directory BIND server boot file BIND server cache file BIND server local host reverse address host file BIND primary server hosts file BIND primary server reverse address hosts file BIND data file See Also nslookup(1), hesiod(3), hesiod.conf(5), svc.conf(5), svcsetup(8), named(8), krb.conf(5), resolv.conf(5) Guide to the BIND/Hesiod Service Guide to Kerberos bindsetup(8)
