named - インターネット・ドメイン名サーバ(DNS)
NAMED [-d debuglevel] [-p port#] [-(b|c) config_file] [-f -q -r]
[-u user_name] [-g group_name] [-t directory] [-w directory]
[config_file]
Named はインターネット・ドメイン名サーバです。インターネット・ ネームドメインシステムに関する詳細については、RFC 1033,1034, 1035 を参照してください。引数が与えられない場合、named はデフォルトの 設定ファイルである /etc/named.conf を読みに行き、初期化データを 読み込んだ後、問い合わせを待ちます。コマンドラインの最後で config_file 引数が与えられると、``-b'' または ``-c'' フラグで 与えられた設定ファイルの指定に優先します。
注意：named のオプションのうちのいくつかで指定できる動作は、 設定ファイルの中でも制御できます。詳細については、BIND ディストリ ビューションに含まれる設定ファイルのガイドを参照してください。
オプションは以下の通りです。
デバッグ情報を表示します。表示されるメッセージのレベルを debuglevel で指定します。負の値が与えられると、debuglevel は 1 にセットされます。
注意：古いバージョンの NAMED に比べて、新しいデバッギング・ フレームワークは、かなり洗練されています。設定ファイル中の ``logging'' ステートメントでは、多岐に渡るカテゴリ（問い合 わせや転送入力／出力など）におけるイベント・セットごとに、 複数の限定可能なデバッグレベルを許しています。これら、 拡張された新しい機能についての詳細は、BIND ディストリビュ ーションに含まれる設定ファイルのガイドを参照してください。
Use the specified remote port number; this is the port number to which NAMED will send queries. The default value is the standard port number, i.e., the port number returned by getservbyname(3) for service ``domain''.
NOTE: Previously, the syntax ``-p port#[/localport#]'' was supported; the first port was that used when contacting remote servers, and the second one was the service port bound by the local instance of NAMED. The current usage is equivalent to the old usage without the localport# specified; this functionality can be specified with the ``listen-on'' clause of the configuration file's ``options'' statement.
Use an alternate config_file; this argument is overridden by any config_file which is specified at the end of the command line. The default value is /etc/named.conf.
このプロセスをフォアグラウンドで実行します。fork(2) して デーモン化することはしません（デフォルトではデーモン化 されます）。
Trace all incoming queries if NAMED has been compiled with QRYLOG defined.
NOTE: This option is deprecated in favor of the ``queries'' logging category of the configuration file's ``logging'' statement; for more information, please refer to the configuration file guide included with this distribution of BIND.
Turns recursion off in the server. Answers can come only from local (primary or secondary) zones. This can be used on root servers. The default is to use recursion.
NOTE: This option can be overridden by and is deprecated in favor of the ``recursion'' clause of the configuration file's ``options'' statement.
Specifies the user the server should run as after it initializes. The value specified may be either a username or a numeric user id. If the ``-g'' flag is not specified, then the group id used will be the primary group of the user specified (initgroups() is called, so all of the user's groups will be available to the server).
Specifies the group the server should run as after it initializes. The value specified may be either a groupname or a numeric group id.
Specifies the directory the server should chroot() into as soon as it is finshed processing command line arguments.
Sets the working directory of the server. The ``directory'' clause of the configuration file's ``options'' statement overrides any value specified on the command line. The default working directory is the current directory(``.'').
Any additional argument is taken as the name of the configuration file, for compatibility with older implementations; as noted above, this argument overrides any config_file specified by the use of the ``-b'' or ``-c'' flags. If no further argument is given, then the default configuration file is used (/etc/named.conf).
The master file consists of control information and a list of resource records for objects in the zone of the forms:
$INCLUDE
$ORIGIN
ここで、
is ``.'' for root, ``@'' for the current origin, or a standard domain name. If domain is a standard domain name that does not end with ``.'', the current origin is appended to the domain. Domain names ending with ``.'' are unmodified.
This field is used to define an origin for the data in an included file. It is equivalent to placing an $ORIGIN statement before the first line of the included file. The field is optional. Neither the opt_domain field nor $ORIGIN statements in the included file modify the current origin for this file.
An optional integer number for the time-to-live field. It defaults to zero, meaning the minimum value specified in the SOA record for the zone.
The object address type; currently only one type is supported, IN, for objects connected to the DARPA Internet.
This field contains one of the following tokens; the data expected in the resource_record_data field is in parentheses:
Resource records normally end at the end of a line, but may be continued across lines between opening and closing parentheses. Comments are introduced by semicolons and continue to the end of the line.
NOTE: There are other resource record types not shown here. You should consult the BIND Operations Guide (``BOG'') for the complete list. Some resource record types may have been standardized in newer RFC's but not yet implemented in this version of BIND.
Each master zone file should begin with an SOA record for the zone. An example SOA record is as follows:
@ IN SOA ucbvax.Berkeley.EDU. rwh.ucbvax.Berkeley.EDU. (
1989020501 ; serial
10800 ; refresh
3600 ; retry
3600000 ; expire
86400 ) ; minimum
The SOA specifies a serial number, which should be changed each time the master file is changed. Note that the serial number can be given as a dotted number, but this is a very unwise thing to do since the translation to normal integers is via concatenation rather than multiplication and addition. You can spell out the year, month, day of month, and 0..99 version number and still fit inside the unsigned 32-bit size of this field. (It's true that we will have to rethink this strategy in the year 4294, but we're not worried about it.)
Secondary servers check the serial number at intervals specified by the refresh time in seconds; if the serial number changes, a zone transfer will be done to load the new data. If a master server cannot be contacted when a refresh is due, the retry time specifies the interval at which refreshes should be attempted. If a master server cannot be contacted within the interval given by the expire time, all data from the zone is discarded by secondary servers. The minimum value is the time-to-live (``TTL'') used by records in the file with no explicit time-to-live value.
The boot file directives ``domain'' and ``suffixes'' have been obsoleted by a more useful, resolver-based implementation of suffixing for partially-qualified domain names. The prior mechanisms could fail under a number of situations, especially when then local nameserver did not have complete information.
The following signals have the specified effect when sent to the server process using the kill(1) command:
/etc/named.conf default name server configuration file /var/run/named.pid (_PATH_PIDFILE) the process id /var/tmp/named_dump.db (_PATH_DUMPFILE) dump of the name server database /var/tmp/named.run (file: _PATH_DEBUG) debug output /var/tmp/named.stats (file: _PATH_STATS) nameserver statistics data
gethostbyname(3), hostname(7), kill(1), resolver(3), resolver(5), signal(2), RFC 882, RFC 883, RFC 973, RFC 974, RFC 1033, RFC 1034, RFC 1035, RFC 1123, ``Name Server Operations Guide for BIND''