|
|
1.1 root 1: .\" Copyright (c) 1986, 1988 Regents of the University of California.
2: .\" All rights reserved.
3: .\"
4: .\" Redistribution and use in source and binary forms are permitted
5: .\" provided that this notice is preserved and that due credit is given
6: .\" to the University of California at Berkeley. The name of the University
7: .\" may not be used to endorse or promote products derived from this
8: .\" software without specific prior written permission. This software
9: .\" is provided ``as is'' without express or implied warranty.
10: .\"
11: .\" @(#)manage.me 6.7 (Berkeley) 12/14/89
12: .\"
13: .sh 1 "Domain Management"
14: .pp
15: This section contains information for starting,
16: controlling and debugging \fInamed\fP.
17: .sh 2 /etc/rc.local
18: .pp
19: The hostname should be set to the full domain style name in \fI/etc/rc.local\fP
20: using \fIhostname\|(1)\fP.
21: The following entry should be added to \fI/etc/rc.local\fP to start
22: up \fInamed\fP at system boot time:
23: .(b l
24: \fIif [ -f /etc/named ]; then
25: /etc/named\fP [options] \fI& echo -n ' named' >/dev/console\fP
26: \fIfi\fP
27: .)b
28: This usually directly follows the lines that start \fIsyslogd\fP.
29: \fBDo Not\fP attempt to run \fInamed\fP from \fIinetd\fP.
30: This will
31: continuously restart the name server and defeat the purpose of having a cache.
32: .sh 2 /etc/named.pid
33: .pp
34: When \fInamed\fP is successfully started up it writes its process id
35: into the file \fI/etc/named.pid\fP. This is useful to programs
36: that want to send signals to \fInamed\fP. The name of this file may be changed
37: by defining \fIPIDFILE\fP to the new name when compiling \fInamed\fP.
38: .sh 2 /etc/hosts
39: .pp
40: The \fIgethostbyname\|()\fP library call can detect if \fInamed\fP is running.
41: If it is determined that \fInamed\fP is not running it will look in
42: \fI/etc/hosts\fP to resolve an address.
43: This option was added to allow \fIifconfg\|(8C)\fP to configure the machines
44: local interfaces and to enable a system manager to access the network
45: while the system is in single user mode.
46: It is advisable to put the local machines interface addresses and a couple of
47: machine names and address in
48: \fI/etc/hosts\fP so the system manager can rcp files from another machine
49: when the system is in single user mode.
50: The format of \fI/etc/host\fP has not changed. See \fIhosts\|(5)\fP
51: for more information.
52: Since the process of reading \fI/etc/hosts\fP is slow,
53: it is not advised to use this option when the system is in multi user mode.
54:
55: .sh 2 Signals
56: .pp
57: There are several signals that can be sent to the \fInamed\fP process
58: to have it do tasks without restarting the process.
59: .sh 3 Reload
60: .pp
61: SIGHUP -
62: Causes \fInamed\fP to read \fInamed.boot\fP and reload the database.
63: All previously cached data is lost.
64: This is useful when you have made a change to a data file
65: and you want \fInamed\fP\|'s internal database to reflect the change.
66: .sh 3 Debugging
67: .pp
68: When \fInamed\fP is running incorrectly, look first in
69: \fI/usr/adm/messages\fP and check for any messages logged by \fIsyslog\fP.
70: Next send it a signal to see what is happening.
71: .pp
72: SIGINT -
73: Dumps the current data base and cache to
74: \fI/usr/\|tmp/\|named_dump\|.\|db\fP
75: This should give you an indication to whether the data base was loaded
76: correctly.
77: The name of the dump file may be changed
78: by defining \fIDUMPFILE\fP to the new name when compiling \fInamed\fP.
79:
80: \fINote:\fP the following two signals only work when \fInamed\fP is built with
81: \fIDEBUG\fP defined.
82: .pp
83: SIGUSR1 -
84: Turns on debugging. Each following USR1 increments the debug level.
85: The output goes to \fI/usr/tmp/named.run\fP
86: The name of this debug file may be changed
87: by defining \fIDEBUGFILE\fP to the new name before compiling \fInamed\fP.
88: .pp
89: SIGUSR2 -
90: Turns off debugging completely.
91:
92: For more detailed debugging, define DEBUG when compiling the resolver
93: routines into \fI/lib/libc.a\fP.
94: .sx 0
95: .sp 2
96: .ce
97: .b ACKNOWLEDGEMENTS
98: .pp
99: Many thanks to the users at U.C. Berkeley for falling into many of the
100: holes involved with integrating BIND into the system so that others
101: would be spared the trauma. I would also like to extend gratitude to
102: Jim McGinness and Digital Equipment Corporation for permitting
103: me to spend most of my time on this project.
104: .pp
105: Ralph Campbell, Doug Kingston, Craig Partridge, Smoot Carl-Mitchell,
106: Mike Muuss and everyone else on the DARPA Internet who has contributed
107: to the development of BIND.
108: To the members of the original BIND project, Douglas Terry, Mark Painter,
109: David Riggle and Songnian Zhou.
110: .pp
111: Anne Hughes, Jim Bloom and Kirk McKusick and the many others who have
112: reviewed this paper giving considerable advice.
113: .pp
114: This work was sponsored by the Defense Advanced Research Projects Agency
115: (DoD), Arpa Order No. 4871 monitored by the Naval Electronics Systems
116: Command under contract No. N00039-84-C-0089.
117: The views and conclusions contained in this document are those of the
118: authors and should not be interpreted as representing official policies,
119: either expressed or implied, of the Defense Research Projects Agency,
120: of the US Government, or of Digital Equipment Corporation.
121: .bp
122: .ba 0
123: .in 0
124: .sp 2
125: .ce
126: .b REFERENCES
127: .sp
128: .nr ii 1i
129: .ip [Birrell]
130: Birrell, A. D.,
131: Levin, R.,
132: Needham, R. M.,
133: and Schroeder, M.D.,
134: .q "Grapevine: An Exercise in Distributed Computing."
135: In
136: .ul
137: Comm. A.C.M. 25,
138: 4:260-274
139: April 1982.
140: .ip [RFC819]
141: Su, Z.
142: Postel, J.,
143: .q "The Domain Naming Convention for Internet User Applications."
144: .ul
145: Internet Request For Comment 819
146: Network Information Center,
147: SRI International,
148: Menlo Park, California.
149: August 1982.
150: .ip [RFC974]
151: Partridge, C.,
152: .q "Mail Routing and The Domain System."
153: .ul
154: Internet Request For Comment 974
155: Network Information Center,
156: SRI International,
157: Menlo Park, California.
158: February 1986.
159: .ip [RFC1032]
160: Stahl, M.,
161: .q "Domain Administrators Guide"
162: .ul
163: Internet Request For Comment 1032
164: Network Information Center,
165: SRI International,
166: Menlo Park, California.
167: November 1987.
168: .ip [RFC1033]
169: Lottor, M.,
170: .q "Domain Administrators Guide"
171: .ul
172: Internet Request For Comment 1033
173: Network Information Center,
174: SRI International,
175: Menlo Park, California.
176: November 1987.
177: .ip [RFC1034]
178: Mockapetris, P.,
179: .q "Domain Names - Concept and Facilities."
180: .ul
181: Internet Request For Comment 1034
182: Network Information Center,
183: SRI International,
184: Menlo Park, California.
185: November 1987.
186: .ip [RFC1035]
187: Mockapetris, P.,
188: .q "Domain Names - Implementation and Specification."
189: .ul
190: Internet Request For Comment 1035
191: Network Information Center,
192: SRI International,
193: Menlo Park, California.
194: November 1987.
195: .ip [RFC1101]
196: Mockapetris, P.,
197: .q "DNS Encoding of Network Names and Other Types."
198: .ul
199: Internet Request For Comment 1101
200: Network Information Center,
201: SRI International,
202: Menlo Park, California.
203: April 1989.
204: .ip [Terry]
205: Terry, D. B.,
206: Painter, M.,
207: Riggle, D. W.,
208: and
209: Zhou, S.,
210: .ul
211: The Berkeley Internet Name Domain Server.
212: Proceedings USENIX Summer Conference,
213: Salt Lake City, Utah.
214: June 1984, pages 23-31.
215: .ip [Zhou]
216: Zhou, S.,
217: .ul
218: The Design and Implementation of the Berkeley Internet Name Domain (BIND) Servers.
219: UCB/CSD 84/177.
220: University of California, Berkeley,
221: Computer Science Division.
222: May 1984.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.