Penguin
Recent Changes
Annotated edit history of named(8) version 3, including all changes. View license author blame.
Rev Author # Line
1 perry 1 ----
3 MikeBeattie 2
1 perry 3 !!NAME
4
5 named - Internet domain name server (DNS)
3 MikeBeattie 6
1 perry 7 !!SYNOPSIS
8
3 MikeBeattie 9 named [[-d debuglevel] [[-p port#] [[ -(b|c) config_file] [[-f -q -r -v] [[-u user_name] [[-g group_name][[-t directory] [[-w directory] [[config_file]
1 perry 10
11 !!DESCRIPTION
12
13 Named is the Internet domain name server. See RFC's 1033,
14 1034, and 1035 for more information on the Internet
15 name-domain system. Without any arguments, named will read
16 the default configuration file
17 /etc/bind/named.conf, read any initial data, and
18 listen for queries. A config_file argument given at the end
19 of the command line will override any config_file specified
20 by using the ``-b'' or ``-c'' flags.
21
22
23 __NOTE__: Several of named's options, and much more of its behaviour, can be controlled in the configuration file. Please refer to the configuration file guide included with this __BIND__ distribution for further information.
24
25
26 Options are:
27 -d debuglevel
28
29
30 Print debugging information. The debuglevel is anumber determines the level of messages printed.If negative, debuglevel is set to ``1''.__NOTE__: The new debugging framework is considerablymore sophisticated than it was in older versionsof named. The configuration file's ``logging'' statement allows for multiple, distinct levels of debugging for each of a large set of categories of events (such as queries, transfers in or out, etc.). Please refer to the configuration file guide included with this __BIND__ distribution for further information about these extensive new capabilities.
31
32
33 -p port#
34 Use the specified remote port number; this is the port
35 number to which named will send queries. The default value
36 is the standard port number, i.e., the port number returned
37 by getservbyname(3) for service
38 ``domain''.
39
40
41 __NOTE__: Previously, the syntax ``-p
42 port#[[/localport#]'' was supported; the first port was that
43 used when contacting ''remote'' servers, and the second
44 one was the service port bound by the ''local'' instance
45 of named. The cur- rent usage is equivalent to the old usage
46 without the localport# specified; this functionality can be
47 specified with the ``listen-on'' clause of the
48 configuration file's ``options''
49 statement.
50
51
3 MikeBeattie 52 -(b|c) config_file
1 perry 53 Use an alternate config_file; this argument is overridden by
54 any config_file which is specified at the end of the command
55 line. The default value is
56 /etc/bind/named.conf.
57
58
59 -f
60 Run this process in the foreground; don't fork(2)
61 and daemonize. (The default is to daemonize.)
62
63
64 -q
65 Trace all incoming queries if named has been com- piled with
66 QRYLOG defined.
67
68
69 __NOTE__: This option is deprecated in favor of the
70 ``queries'' ''logging category'' of the
71 configuration file's ``logging'' statement; for
72 more informa- tion, please refer to the configuration file
73 guide included with this distribution of
74 __BIND__.
75
76
77 -r
78 Turns recursion off in the server. Answers can come only
79 from local (primary or secondary) zones. This can be used on
80 root servers. The default is to use recursion.
81
82
83 __NOTE__: This option can be overridden by and is
84 deprecated in favor of the ``recursion'' clause of
85 the configuration file's ``options'' state-
86 ment.
87
88
89 -v
90 Report the version and exit.
91
92
93 -u user_name
94 Specifies the user the server should run as after it
95 initializes. The value specified may be either a username or
96 a numeric user id. If the ``-g'' flag is not specified, then
97 the group id used will be the primary group of the user
98 speci- fied (initgroups() is called, so all of the user's
99 groups will be available to the server).
100
101
102 -g group_name
103 Specifies the group the server should run as after it
104 initializes. The value specified may be either a groupname
105 or a numeric group id.
106
107
108 -t directory
109 Specifies the directory the server should chroot() into as
110 soon as it is finshed processing command line
111 arguments.
112
113
114 -w directory
115 Sets the working directory of the server. The
116 ``directory'' clause of the configuration file's
117 ``options'' statement overrides any value speci-
118 fied on the command line. The default working directory is
119 the current directory (``.'').
120
121
122 Any additional argument is taken as the name of the configu-
123 ration file, for compatibility with older implementations;
124 as noted above, this argument overrides any config_file
125 specified by the use of the ``-b'' or ``-c'' flags. If no
126 further argument is given, then the default configuration
127 file is used (/etc/bind/named.conf).
128
129
130 __Master File Format__
131 The master file consists of control information and a list
132 of resource records for objects in the zone of the
133 forms:
134
135
136 $INCLUDE
137 where:
138 domain is ``.
139 '' for root, ``@'' for the current ori- gin, or
140 a standard domain name. If domain is a standard domain name
141 that does ''not'' end with ``.'', the current
142 origin is appended to the domain. Domain names ending with
143 ``.'' are unmodified.
144
145
146 opt_domain
147 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.
148
149
150 ttl
151 A integer number that sets the default time-to-live for
152 future records without an explicit ttl.
153
154
155 opt_ttl
156 An optional integer number for the time-to-live field. If
157 not set the ttl is taken from the last $TTL statement. If no
158 $TTL statement has occurred then the SOA minimum value is
159 used and a warning is generated.
160
161
162 opt_class
163 The object address type; currently only one type is
164 supported, IN, for objects connected to the DARPA
165 Internet.
166
167
168 type
169 This field contains one of the following tokens; the data
170 expected in the resource_record_data field is in
171 parentheses:
172
173
174 ; A : a host address (dotted-quad IP address)
175
176
177 ; NS : an authoritative name server (domain)
178
179
180 ; MX : a mail exchanger (domain), pre- ceded by a preference value
181 (0..32767), with lower numeric values representing higher
182 log- ical preferences.
183
184
185 ; CNAME : the canonical name for an alias (domain)
186
187
188 ; SOA : marks the start of a zone of authority (domain of originat-
189 ing host, domain address of maintainer, a serial number and
190 the following parameters in seconds: refresh, retry, expire
191 and minimum TTL (see RFC 883 and RFC 2308)).
192
193
194 ; NULL:a null resource record (no format or data)
195
196
197 ; RP : a Responsible Person for some domain name (mailbox,
198 TXT-referral)
199
200
201 ; PTR : a domain name pointer (domain)
202
203
204 ; HINFO : host information (cpu_type OS_type)
205
206
207 Resource records normally end at the end of a line, but may
208 be continued across lines between opening and closing paren-
209 theses. Comments are introduced by semicolons and continue
210 to the end of the line.
211
212
213 __NOTE__: There are other resource record types not shown
214 here. You should consult the __BIND__ Operations Guide
215 (``BOG'') for the complete list. Some resource record types
216 may have been standardized in newer RFC's but not yet
217 implemented in this version of __BIND__.
218
219
220 !!SOA Record Format
221 Each master zone file should begin with an SOA record for
222 the zone. An example SOA record is as follows:
223
224
225 @ IN SOA ucbvax.Berkeley.EDU. rwh.ucbvax.Berkeley.EDU. (
226 1989020501 ; serial
227 10800 ; refresh
228 3600 ; retry
229 3600000 ; expire
230 86400 ) ; minimum
231 The SOA specifies a serial number, which should be incre- mented 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 wor- ried about it.)
232
233
234 Secondary servers check the serial number at intervals spec-
235 ified by the refresh time in seconds; if the serial number
236 changes, a zone transfer will be done to load the new data.
237 If a master server cannot be contacted when a refresh is
238 due, the retry time specifies the interval at which
239 refreshes should be attempted. If a master server cannot be
240 contacted within the interval given by the expire time, all
241 data from the zone is discarded by secondary servers. The
242 minimum value is the cache time-to-live for negative answers
243 (RFC 2308).
244
245 !!NOTES
246
247
248 The boot file directives ``domain'' and
249 ``suffixes'' have been obsoleted by a more useful,
250 resolver-based implementa- tion of suffixing for
251 partially-qualified domain names. The prior mechanisms could
252 fail under a number of situations, especially when then
253 local nameserver did not have complete
254 information.
255
256
257 The following signals have the specified effect when sent to the server process using the kill(1) command
258
259 ; SIGHUP : Causes server to read named.conf and reload the
260 database. If the server is built with the
261 FORCED_RELOAD compile-time option, then
262 SIGHUP will also cause the server to check the
263 serial number on all secondary zones; normally, the serial
264 numbers are only checked at the SOA-specified intervals.
265
266
267 ; SIGINT : Dumps the current data base and cache to ``/var/cache/bind/named_dump.db'' or the value of _PATH_DUMPFILE.
268
269
270 ; SIGILL : Dumps statistics data into named.stats if the
271 server is compiled with -DSTATS. Statistics data is
272 appended to the file.
273
274
275 ; SIGSYS : Dumps the profiling data in /var/tmp if the server
276 is compiled with profiling (server forks, chdirs and
277 exits).
278
279
280 ; SIGTERM : Saves any modified dynamic zones to the file system, and shuts down the server.
281
282
283 ; SIGUSR1 : Turns on debugging; each SIGUSR1 increments debug level. (SIGEMT on older systems without SIGUSR1. )
284
285
286 ; SIGUSR2 : Turns off debugging completely. (SIGFPE on older systems without SIGUSR2.)
287
288
289 ; SIGWINCH : Toggles logging of all incoming queries via
290 syslog(3) (requires server to have been built with
291 the QRYLOG option).
292
293
294 !!FILES
295 /etc/bind/named.conf
296 default name server configura- tion
297 file
298
299
300 /var/run/named.pid (_PATH_PIDFILE)
301 the pro- cess id
302 /var/cache/bind/named_dump.db
303 (_PATH_DUMPFILE)
304 dump of the name server database
305 /var/tmp/named.run (file: _PATH_DEBUG)
306 debug out- put
307 /var/tmp/named.stats (file: _PATH_STATS)
308 nameserver statistics data
309
310 !!SEE ALSO
311
312 named.conf(5), gethostbyname(3),
313 hostname(7), kill(1),
314 resolver(3), resolver(5),
2 perry 315 signal(3), !NamedNotes, RFC 882, RFC 883, RFC 973, RFC 974, RFC
1 perry 316 1033, RFC 1034, RFC 1035, RFC 1123, RFC 2308 ``Name Server
317 Operations Guide for __BIND__''
318
319
2 perry 320 4th Berkeley !DistributionFebruary 1, 1996 1
1 perry 321 ----
3 MikeBeattie 322
323 CategoryDns
This page is a man page (or other imported legacy content). We are unable to automatically determine the license status of this page.

PHP Warning

lib/blame.php:177: Warning: Invalid argument supplied for foreach() (...repeated 3 times)