.\" Copyright (c) 1986, 1988 The Regents of the University of California.
.\" Redistribution and use in source and binary forms, with or without
.\" modification, are permitted provided that the following conditions
.\" 1. Redistributions of source code must retain the above copyright
.\" notice, this list of conditions and the following disclaimer.
.\" 2. Redistributions in binary form must reproduce the above copyright
.\" notice, this list of conditions and the following disclaimer in the
.\" documentation and/or other materials provided with the distribution.
.\" 3. All advertising materials mentioning features or use of this software
.\" must display the following acknowledgement:
.\" This product includes software developed by the University of
.\" California, Berkeley and its contributors.
.\" 4. Neither the name of the University nor the names of its contributors
.\" may be used to endorse or promote products derived from this software
.\" without specific prior written permission.
.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
.\" @(#)manage.me 6.9 (Berkeley) 4/22/91
.sh 1 "Domain Management"
This section contains information for starting,
controlling and debugging \fInamed\fP.
The hostname should be set to the full domain style name in \fI/etc/rc.local\fP
using \fIhostname\|(1)\fP.
The following entry should be added to \fI/etc/rc.local\fP to start
up \fInamed\fP at system boot time:
\fIif [ -f /etc/named ]; then
/etc/named\fP [options] \fI& echo -n ' named' >/dev/console\fP
This usually directly follows the lines that start \fIsyslogd\fP.
\fBDo Not\fP attempt to run \fInamed\fP from \fIinetd\fP.
continuously restart the name server and defeat the purpose of having a cache.
When \fInamed\fP is successfully started up it writes its process id
into the file \fI/etc/named.pid\fP. This is useful to programs
that want to send signals to \fInamed\fP. The name of this file may be changed
by defining \fIPIDFILE\fP to the new name when compiling \fInamed\fP.
The \fIgethostbyname\|()\fP library call can detect if \fInamed\fP is running.
If it is determined that \fInamed\fP is not running it will look in
\fI/etc/hosts\fP to resolve an address.
This option was added to allow \fIifconfig\|(8C)\fP to configure the machines
local interfaces and to enable a system manager to access the network
while the system is in single user mode.
It is advisable to put the local machines interface addresses and a couple of
machine names and address in
\fI/etc/hosts\fP so the system manager can rcp files from another machine
when the system is in single user mode.
The format of \fI/etc/host\fP has not changed. See \fIhosts\|(5)\fP
Since the process of reading \fI/etc/hosts\fP is slow,
it is not advised to use this option when the system is in multi user mode.
There are several signals that can be sent to the \fInamed\fP process
to have it do tasks without restarting the process.
Causes \fInamed\fP to read \fInamed.boot\fP and reload the database.
All previously cached data is lost.
This is useful when you have made a change to a data file
and you want \fInamed\fP\|'s internal database to reflect the change.
When \fInamed\fP is running incorrectly, look first in
\fI/usr/adm/messages\fP and check for any messages logged by \fIsyslog\fP.
Next send it a signal to see what is happening.
Dumps the current data base and cache to
\fI/usr/\|tmp/\|named_dump\|.\|db\fP
This should give you an indication to whether the data base was loaded
The name of the dump file may be changed
by defining \fIDUMPFILE\fP to the new name when compiling \fInamed\fP.
\fINote:\fP the following two signals only work when \fInamed\fP is built with
Turns on debugging. Each following USR1 increments the debug level.
The output goes to \fI/usr/tmp/named.run\fP
The name of this debug file may be changed
by defining \fIDEBUGFILE\fP to the new name before compiling \fInamed\fP.
Turns off debugging completely.
For more detailed debugging, define DEBUG when compiling the resolver
routines into \fI/lib/libc.a\fP.
Many thanks to the users at U.C. Berkeley for falling into many of the
holes involved with integrating BIND into the system so that others
would be spared the trauma. I would also like to extend gratitude to
Jim McGinness and Digital Equipment Corporation for permitting
me to spend most of my time on this project.
Ralph Campbell, Doug Kingston, Craig Partridge, Smoot Carl-Mitchell,
Mike Muuss and everyone else on the DARPA Internet who has contributed
to the development of BIND.
To the members of the original BIND project, Douglas Terry, Mark Painter,
David Riggle and Songnian Zhou.
Anne Hughes, Jim Bloom and Kirk McKusick and the many others who have
reviewed this paper giving considerable advice.
This work was sponsored by the Defense Advanced Research Projects Agency
(DoD), Arpa Order No. 4871 monitored by the Naval Electronics Systems
Command under contract No. N00039-84-C-0089.
The views and conclusions contained in this document are those of the
authors and should not be interpreted as representing official policies,
either expressed or implied, of the Defense Research Projects Agency,
of the US Government, or of Digital Equipment Corporation.
.q "Grapevine: An Exercise in Distributed Computing."
.q "The Domain Naming Convention for Internet User Applications."
Internet Request For Comment 819
Network Information Center,
.q "Mail Routing and The Domain System."
Internet Request For Comment 974
Network Information Center,
.q "Domain Administrators Guide"
Internet Request For Comment 1032
Network Information Center,
.q "Domain Administrators Guide"
Internet Request For Comment 1033
Network Information Center,
.q "Domain Names - Concept and Facilities."
Internet Request For Comment 1034
Network Information Center,
.q "Domain Names - Implementation and Specification."
Internet Request For Comment 1035
Network Information Center,
.q "DNS Encoding of Network Names and Other Types."
Internet Request For Comment 1101
Network Information Center,
The Berkeley Internet Name Domain Server.
Proceedings USENIX Summer Conference,
The Design and Implementation of the Berkeley Internet Name Domain (BIND) Servers.
University of California, Berkeley,
Computer Science Division.
projects / unix-history / blob