3 d93fca6a 2005-02-11 devnull ndbquery, ndbmkhash, ndbmkdb, ndbipquery, ndbmkhosts \- network database
4 d93fca6a 2005-02-11 devnull .SH SYNOPSIS
5 d93fca6a 2005-02-11 devnull .B ndbquery
10 d93fca6a 2005-02-11 devnull .I "attr value"
15 d93fca6a 2005-02-11 devnull .B ndbipquery
16 d93fca6a 2005-02-11 devnull .I "attr value"
17 d93fca6a 2005-02-11 devnull .I rattr...
19 d93fca6a 2005-02-11 devnull .B ndbmkhash
20 d93fca6a 2005-02-11 devnull .I "file attr"
22 d93fca6a 2005-02-11 devnull .B ndbmkdb
23 d93fca6a 2005-02-11 devnull .SH DESCRIPTION
24 d93fca6a 2005-02-11 devnull The network database holds administrative information used by
25 d93fca6a 2005-02-11 devnull .I authdial
27 d32deab1 2020-08-16 rsc .MR authsrv (3) )
29 d32deab1 2020-08-16 rsc .MR secstored (1) .
31 d93fca6a 2005-02-11 devnull .I Ndbquery
32 d93fca6a 2005-02-11 devnull searches the database for an attribute of type
34 d93fca6a 2005-02-11 devnull and value
35 d93fca6a 2005-02-11 devnull .IR value .
38 d93fca6a 2005-02-11 devnull is not specified, all entries matched by the search are returned.
41 d93fca6a 2005-02-11 devnull is specified, the value of the first pair with attribute
43 d93fca6a 2005-02-11 devnull of all the matched entries is returned.
45 d93fca6a 2005-02-11 devnull .I Ndbipquery
47 d93fca6a 2005-02-11 devnull .I ndbipinfo
49 d32deab1 2020-08-16 rsc .MR ndb (3) )
50 d93fca6a 2005-02-11 devnull to search for the values of the attributes
52 d93fca6a 2005-02-11 devnull corresponding to the system
53 d93fca6a 2005-02-11 devnull with entries of attribute type
57 d93fca6a 2005-02-11 devnull .IR value .
59 d93fca6a 2005-02-11 devnull .I Ndbmkhash
60 d93fca6a 2005-02-11 devnull creates a hash file for all entries with attribute
62 d93fca6a 2005-02-11 devnull in database file
63 d93fca6a 2005-02-11 devnull .IR file .
64 d93fca6a 2005-02-11 devnull The hash files are used by
65 d93fca6a 2005-02-11 devnull .I ndbquery
66 d93fca6a 2005-02-11 devnull and by the ndb library routines.
68 d93fca6a 2005-02-11 devnull .\" .I Ndb/cs
69 d93fca6a 2005-02-11 devnull .\" is a server used by
70 d93fca6a 2005-02-11 devnull .\" .IR dial (2)
71 d93fca6a 2005-02-11 devnull .\" to translate network names.
72 d93fca6a 2005-02-11 devnull .\" It is started at boot time.
73 d93fca6a 2005-02-11 devnull .\" It finds out what networks are configured
74 d93fca6a 2005-02-11 devnull .\" by looking for
75 d93fca6a 2005-02-11 devnull .\" .B /net/*/clone
76 d93fca6a 2005-02-11 devnull .\" when it starts.
77 d93fca6a 2005-02-11 devnull .\" It can also be told about networks by writing
79 d93fca6a 2005-02-11 devnull .\" .B /net/cs
80 d93fca6a 2005-02-11 devnull .\" a message of the form:
82 d93fca6a 2005-02-11 devnull .\" .B "add net1 net2 ..."
84 d93fca6a 2005-02-11 devnull .\" .I Ndb/cs
85 d93fca6a 2005-02-11 devnull .\" also sets the system name in
86 d93fca6a 2005-02-11 devnull .\" .B /dev/sysname
87 d93fca6a 2005-02-11 devnull .\" if it can figure it out.
88 d93fca6a 2005-02-11 devnull .\" The options are:
90 d93fca6a 2005-02-11 devnull .\" .B -f
91 d93fca6a 2005-02-11 devnull .\" supplies the name of the data base file to use,
92 d93fca6a 2005-02-11 devnull .\" default
93 d93fca6a 2005-02-11 devnull .\" .BR /lib/ndb/local .
95 d93fca6a 2005-02-11 devnull .\" .B -x
96 d93fca6a 2005-02-11 devnull .\" specifies the mount point of the
97 d93fca6a 2005-02-11 devnull .\" network.
99 d93fca6a 2005-02-11 devnull .\" .B -n
100 d93fca6a 2005-02-11 devnull .\" causes cs to do nothing but set the system name.
102 d93fca6a 2005-02-11 devnull .\" .I Ndb/csquery
103 d93fca6a 2005-02-11 devnull .\" can be used to query
104 d93fca6a 2005-02-11 devnull .\" .I ndb/cs
105 d93fca6a 2005-02-11 devnull .\" to see how it resolves addresses.
106 d93fca6a 2005-02-11 devnull .\" .I Ndb/csquery
107 d93fca6a 2005-02-11 devnull .\" prompts for addresses and prints out what
108 d93fca6a 2005-02-11 devnull .\" .I ndb/cs
109 d93fca6a 2005-02-11 devnull .\" returns.
110 d93fca6a 2005-02-11 devnull .\" .I Server
111 d93fca6a 2005-02-11 devnull .\" defaults to
112 d93fca6a 2005-02-11 devnull .\" .BR /net/cs .
113 d93fca6a 2005-02-11 devnull .\" If any
114 d93fca6a 2005-02-11 devnull .\" .I addrs
115 d93fca6a 2005-02-11 devnull .\" are specified,
116 d93fca6a 2005-02-11 devnull .\" .I ndb/csquery
117 d93fca6a 2005-02-11 devnull .\" prints their translations and immediately exits.
118 d93fca6a 2005-02-11 devnull .\" The exit status will be nil only if all addresses
119 d93fca6a 2005-02-11 devnull .\" were successfully translated
121 d93fca6a 2005-02-11 devnull .\" .B -s
122 d93fca6a 2005-02-11 devnull .\" flag sets exit status without printing any results.
124 d93fca6a 2005-02-11 devnull .\" .I Ndb/dns
125 d93fca6a 2005-02-11 devnull .\" is a server used by
126 d93fca6a 2005-02-11 devnull .\" .I ndb/cs
127 d93fca6a 2005-02-11 devnull .\" and by remote systems to translate Internet domain names.
128 d93fca6a 2005-02-11 devnull .\" .I Ndb/dns
129 d93fca6a 2005-02-11 devnull .\" is started at boot time.
130 d93fca6a 2005-02-11 devnull .\" By default
131 d93fca6a 2005-02-11 devnull .\" .I dns
132 d93fca6a 2005-02-11 devnull .\" serves only requests written to
133 d93fca6a 2005-02-11 devnull .\" .BR /net/dns .
134 d93fca6a 2005-02-11 devnull .\" The options are:
136 d93fca6a 2005-02-11 devnull .\" .B -f
137 d93fca6a 2005-02-11 devnull .\" supplies the name of the data base file to use,
138 d93fca6a 2005-02-11 devnull .\" default
139 d93fca6a 2005-02-11 devnull .\" .BR /lib/ndb/local .
141 d93fca6a 2005-02-11 devnull .\" .B -x
142 d93fca6a 2005-02-11 devnull .\" specifies the mount point of the
143 d93fca6a 2005-02-11 devnull .\" network.
145 d93fca6a 2005-02-11 devnull .\" .B -s
146 d93fca6a 2005-02-11 devnull .\" also answer domain requests sent to UDP port 53.
148 d93fca6a 2005-02-11 devnull .\" .B -n
149 d93fca6a 2005-02-11 devnull .\" whenever a zone that we serve changes, send UDP NOTIFY
150 d93fca6a 2005-02-11 devnull .\" messages to any dns slaves for that zone.
152 d93fca6a 2005-02-11 devnull .\" .B -z
153 d93fca6a 2005-02-11 devnull .\" whenever we receive a UDP NOTIFY message, run
154 d93fca6a 2005-02-11 devnull .\" .I program
155 d93fca6a 2005-02-11 devnull .\" with the domain name of the area as its argument.
157 d93fca6a 2005-02-11 devnull .\" .B -r
158 d93fca6a 2005-02-11 devnull .\" defer to other servers to resolve queries.
160 d93fca6a 2005-02-11 devnull .\" When the
161 d93fca6a 2005-02-11 devnull .\" .B -r
162 d93fca6a 2005-02-11 devnull .\" option is specified, the servers used come from the
163 d93fca6a 2005-02-11 devnull .\" .I dns
164 d93fca6a 2005-02-11 devnull .\" attribute in the database. For example, to specify a set of dns servers that
165 d93fca6a 2005-02-11 devnull .\" will resolve requests for systems on the network
166 d93fca6a 2005-02-11 devnull .\" .IR mh-net :
169 d93fca6a 2005-02-11 devnull .\" ipnet=mh-net ip=135.104.0.0 ipmask=255.255.0.0
170 d93fca6a 2005-02-11 devnull .\" dns=ns1.cs.bell-labs.com
171 d93fca6a 2005-02-11 devnull .\" dns=ns2.cs.bell-labs.com
172 d93fca6a 2005-02-11 devnull .\" dom=ns1.cs.bell-labs.com ip=135.104.1.11
173 d93fca6a 2005-02-11 devnull .\" dom=ns2.cs.bell-labs.com ip=135.104.1.12
177 d93fca6a 2005-02-11 devnull .\" The server for a domain is indicated by a database entry containing
178 d93fca6a 2005-02-11 devnull .\" both a
179 d93fca6a 2005-02-11 devnull .\" .I dom
180 d93fca6a 2005-02-11 devnull .\" and a
181 d93fca6a 2005-02-11 devnull .\" .I ns
182 d93fca6a 2005-02-11 devnull .\" attribute.
183 d93fca6a 2005-02-11 devnull .\" For example, the entry for the Internet root is:
186 d93fca6a 2005-02-11 devnull .\" dom=
187 d93fca6a 2005-02-11 devnull .\" ns=A.ROOT-SERVERS.NET
188 d93fca6a 2005-02-11 devnull .\" ns=B.ROOT-SERVERS.NET
189 d93fca6a 2005-02-11 devnull .\" ns=C.ROOT-SERVERS.NET
190 d93fca6a 2005-02-11 devnull .\" dom=A.ROOT-SERVERS.NET ip=198.41.0.4
191 d93fca6a 2005-02-11 devnull .\" dom=B.ROOT-SERVERS.NET ip=128.9.0.107
192 d93fca6a 2005-02-11 devnull .\" dom=C.ROOT-SERVERS.NET ip=192.33.4.12
195 d93fca6a 2005-02-11 devnull .\" The last three lines provide a mapping for the
196 d93fca6a 2005-02-11 devnull .\" server names to their ip addresses. This is only
197 d93fca6a 2005-02-11 devnull .\" a hint and will be superseded from whatever is learned
198 d93fca6a 2005-02-11 devnull .\" from servers owning the domain.
200 d93fca6a 2005-02-11 devnull .\" You can also serve a subtree of the domain name space from the local
201 d93fca6a 2005-02-11 devnull .\" database. You indicate subtrees that you'ld like to serve by
202 d93fca6a 2005-02-11 devnull .\" adding an
203 d93fca6a 2005-02-11 devnull .\" .B soa=
204 d93fca6a 2005-02-11 devnull .\" attribute to the root entry.
205 d93fca6a 2005-02-11 devnull .\" For example, the Bell Labs CS research domain is:
208 d93fca6a 2005-02-11 devnull .\" dom=cs.bell-labs.com soa=
209 d93fca6a 2005-02-11 devnull .\" refresh=3600 ttl=3600
210 d93fca6a 2005-02-11 devnull .\" ns=plan9.bell-labs.com
211 d93fca6a 2005-02-11 devnull .\" ns=ns1.cs.bell-labs.com
212 d93fca6a 2005-02-11 devnull .\" ns=ns2.cs.bell-labs.com
213 d93fca6a 2005-02-11 devnull .\" mb=presotto@plan9.bell-labs.com
214 d93fca6a 2005-02-11 devnull .\" mx=mail.research.bell-labs.com pref=20
215 d93fca6a 2005-02-11 devnull .\" mx=plan9.bell-labs.com pref=10
216 d93fca6a 2005-02-11 devnull .\" dnsslave=nslocum.cs.bell-labs.com
217 d93fca6a 2005-02-11 devnull .\" dnsslave=vex.cs.bell-labs.com
220 d93fca6a 2005-02-11 devnull .\" Here, the
221 d93fca6a 2005-02-11 devnull .\" .B mb
222 d93fca6a 2005-02-11 devnull .\" entry is the mail address of the person responsible for the
223 d93fca6a 2005-02-11 devnull .\" domain (default
224 d93fca6a 2005-02-11 devnull .\" .BR postmaster ).
226 d93fca6a 2005-02-11 devnull .\" .B mx
227 d93fca6a 2005-02-11 devnull .\" entries list mail exchangers for the domain name and
228 d93fca6a 2005-02-11 devnull .\" .B refresh
230 d93fca6a 2005-02-11 devnull .\" .B ttl
231 d93fca6a 2005-02-11 devnull .\" define the area refresh interval and the minimum TTL for
232 d93fca6a 2005-02-11 devnull .\" records in this domain.
234 d93fca6a 2005-02-11 devnull .\" .B dnsslave
235 d93fca6a 2005-02-11 devnull .\" entries specify slave DNS servers that should be notified
236 d93fca6a 2005-02-11 devnull .\" when the domain changes. The notification also requires
238 d93fca6a 2005-02-11 devnull .\" .B -n
239 d93fca6a 2005-02-11 devnull .\" flag.
241 d93fca6a 2005-02-11 devnull .\" You can also serve reverse lookups (returning the name that
242 d93fca6a 2005-02-11 devnull .\" goes with an IP address) by adding an
243 d93fca6a 2005-02-11 devnull .\" .B soa=
244 d93fca6a 2005-02-11 devnull .\" attribute to the entry defining the root of the reverse space.
245 d93fca6a 2005-02-11 devnull .\" For example, to provide reverse lookup for all addresses in
246 d93fca6a 2005-02-11 devnull .\" starting with 135.104 you must have a record like:
249 d93fca6a 2005-02-11 devnull .\" dom=104.135.in-addr.arpa soa=
250 d93fca6a 2005-02-11 devnull .\" refresh=3600 ttl=3600
251 d93fca6a 2005-02-11 devnull .\" ns=plan9.bell-labs.com
252 d93fca6a 2005-02-11 devnull .\" ns=ns1.cs.bell-labs.com
253 d93fca6a 2005-02-11 devnull .\" ns=ns2.cs.bell-labs.com
255 d93fca6a 2005-02-11 devnull .\" Notice the form of the reverse address, i.e., it's the bytes of the
256 d93fca6a 2005-02-11 devnull .\" address range you are serving reversed and with
257 d93fca6a 2005-02-11 devnull .\" .B .in-addr.arpa
258 d93fca6a 2005-02-11 devnull .\" appended. This is a standard form for a domain name in an IPv4 PTR record.
260 d93fca6a 2005-02-11 devnull .\" If such an entry exists in the database, reverse addresses will
261 d93fca6a 2005-02-11 devnull .\" automaticly be generated from any IP addresses in the database
262 d93fca6a 2005-02-11 devnull .\" that are under this root. For example
265 d93fca6a 2005-02-11 devnull .\" dom=ns1.cs.bell-labs.com ip=135.104.1.11
267 d93fca6a 2005-02-11 devnull .\" will automaticly create both forward and reverse entries for
268 d93fca6a 2005-02-11 devnull .\" .B ns1.cs.bell-labs.com .
269 d93fca6a 2005-02-11 devnull .\" Unlike other DNS servers, there's no way to generate
270 d93fca6a 2005-02-11 devnull .\" inconsistent forward and reverse entries.
272 d93fca6a 2005-02-11 devnull .\" Delegation of a further subtree to another set of name servers
273 d93fca6a 2005-02-11 devnull .\" is indicated by an
274 d93fca6a 2005-02-11 devnull .\" .B soa=delegated
275 d93fca6a 2005-02-11 devnull .\" attribute.
278 d93fca6a 2005-02-11 devnull .\" dom=bignose.cs.research.bell-labs.com
279 d93fca6a 2005-02-11 devnull .\" soa=delegated
280 d93fca6a 2005-02-11 devnull .\" ns=anna.cs.research.bell-labs.com
281 d93fca6a 2005-02-11 devnull .\" ns=dj.cs.research.bell-labs.com
284 d93fca6a 2005-02-11 devnull .\" Nameservers within the delegated domain (as in this example)
285 d93fca6a 2005-02-11 devnull .\" must have their IP addresses listed elsewhere in
286 d93fca6a 2005-02-11 devnull .\" .I ndb
287 d93fca6a 2005-02-11 devnull .\" files.
289 d93fca6a 2005-02-11 devnull .\" Wild-carded domain names can also be used.
290 d93fca6a 2005-02-11 devnull .\" For example, to specify a mail forwarder for all Bell Labs research systems:
293 d93fca6a 2005-02-11 devnull .\" dom=*.research.bell-labs.com
294 d93fca6a 2005-02-11 devnull .\" mx=research.bell-labs.com
297 d93fca6a 2005-02-11 devnull .\" `Cname' aliases may be established by adding a
298 d93fca6a 2005-02-11 devnull .\" .B cname
299 d93fca6a 2005-02-11 devnull .\" attribute giving the real domain name;
300 d93fca6a 2005-02-11 devnull .\" the name attached to the
301 d93fca6a 2005-02-11 devnull .\" .B dom
302 d93fca6a 2005-02-11 devnull .\" attribute is the alias.
303 d93fca6a 2005-02-11 devnull .\" `Cname' aliases are severely restricted;
304 d93fca6a 2005-02-11 devnull .\" the aliases may have no other attributes than
305 d93fca6a 2005-02-11 devnull .\" .B dom
306 d93fca6a 2005-02-11 devnull .\" and are daily further restricted in their use by new RFCs.
309 d93fca6a 2005-02-11 devnull .\" cname=anna.cs.research.bell-labs.com dom=www.cs.research.bell-labs.com
312 d93fca6a 2005-02-11 devnull .\" .I Ndb/dnsquery
313 d93fca6a 2005-02-11 devnull .\" can be used to query
314 d93fca6a 2005-02-11 devnull .\" .I ndb/dns
315 d93fca6a 2005-02-11 devnull .\" to see how it resolves requests.
316 d93fca6a 2005-02-11 devnull .\" .I Ndb/dnsquery
317 d93fca6a 2005-02-11 devnull .\" prompts for commands of the form
319 d93fca6a 2005-02-11 devnull .\" .I "domain-name request-type"
321 d93fca6a 2005-02-11 devnull .\" where
322 d93fca6a 2005-02-11 devnull .\" .I request-type
323 d93fca6a 2005-02-11 devnull .\" can be
324 d93fca6a 2005-02-11 devnull .\" .BR ip ,
325 d93fca6a 2005-02-11 devnull .\" .BR mx ,
326 d93fca6a 2005-02-11 devnull .\" .BR ns ,
327 d93fca6a 2005-02-11 devnull .\" .BR cname ,
328 d93fca6a 2005-02-11 devnull .\" .BR ptr ....
329 d93fca6a 2005-02-11 devnull .\" In the case of the inverse query type,
330 d93fca6a 2005-02-11 devnull .\" .BR ptr ,
331 d93fca6a 2005-02-11 devnull .\" .I dnsquery
332 d93fca6a 2005-02-11 devnull .\" will reverse the ip address and tack on the
333 d93fca6a 2005-02-11 devnull .\" .B .in-addr.arpa
334 d93fca6a 2005-02-11 devnull .\" for you.
336 d93fca6a 2005-02-11 devnull .\" .I Ndb/dnsdebug
337 d93fca6a 2005-02-11 devnull .\" is like
338 d93fca6a 2005-02-11 devnull .\" .I ndb/dnsquery
339 d93fca6a 2005-02-11 devnull .\" but bypasses the local server.
340 d93fca6a 2005-02-11 devnull .\" It communicates via UDP with the domain name servers
341 d93fca6a 2005-02-11 devnull .\" in the same way that the local resolver would and displays
342 d93fca6a 2005-02-11 devnull .\" all packets received.
343 d93fca6a 2005-02-11 devnull .\" The query can be specified on the command line or
344 d93fca6a 2005-02-11 devnull .\" can be prompted for.
345 d93fca6a 2005-02-11 devnull .\" The queries look like those of
346 d93fca6a 2005-02-11 devnull .\" .I ndb/dnsquery
347 d93fca6a 2005-02-11 devnull .\" with one addition.
348 d93fca6a 2005-02-11 devnull .\" .I Ndb/dnsdebug
349 d93fca6a 2005-02-11 devnull .\" can be directed to query a particular name server by
350 d93fca6a 2005-02-11 devnull .\" the command
351 d93fca6a 2005-02-11 devnull .\" .BI @ name-server\f1.
352 d93fca6a 2005-02-11 devnull .\" From that point on, all queries go to that name server
353 d93fca6a 2005-02-11 devnull .\" rather than being resolved by
354 d93fca6a 2005-02-11 devnull .\" .IR dnsdebug .
356 d93fca6a 2005-02-11 devnull .\" .B @
357 d93fca6a 2005-02-11 devnull .\" command returns query resolution to
358 d93fca6a 2005-02-11 devnull .\" .IR dnsdebug .
359 d93fca6a 2005-02-11 devnull .\" Finally, any command preceded by a
360 d93fca6a 2005-02-11 devnull .\" .BI @ name-server
361 d93fca6a 2005-02-11 devnull .\" sets the name server only for that command.
363 d93fca6a 2005-02-11 devnull .\" Normally
364 d93fca6a 2005-02-11 devnull .\" .I dnsdebug
365 d93fca6a 2005-02-11 devnull .\" uses the
366 d93fca6a 2005-02-11 devnull .\" .B /net
367 d93fca6a 2005-02-11 devnull .\" interface and the database file
368 d93fca6a 2005-02-11 devnull .\" .BR /lib/ndb/local.
370 d93fca6a 2005-02-11 devnull .\" .B -x
371 d93fca6a 2005-02-11 devnull .\" option directs
372 d93fca6a 2005-02-11 devnull .\" .I dnsdebug
373 d93fca6a 2005-02-11 devnull .\" to use the
374 d93fca6a 2005-02-11 devnull .\" .B /net.alt
375 d93fca6a 2005-02-11 devnull .\" interface and
376 d93fca6a 2005-02-11 devnull .\" .B /lib/ndb/external
377 d93fca6a 2005-02-11 devnull .\" file.
379 d93fca6a 2005-02-11 devnull .\" .B -r
380 d93fca6a 2005-02-11 devnull .\" option is the same as for
381 d93fca6a 2005-02-11 devnull .\" .IR ndb/dns .
383 d93fca6a 2005-02-11 devnull .I Ndbmkdb
384 d93fca6a 2005-02-11 devnull is used in concert with
386 d93fca6a 2005-02-11 devnull scripts to convert
387 d93fca6a 2005-02-11 devnull uucp systems files and IP host files
388 d93fca6a 2005-02-11 devnull into database files.
389 d93fca6a 2005-02-11 devnull It is very specific to the situation at Murray Hill.
391 d93fca6a 2005-02-11 devnull When the database files change underfoot,
392 d93fca6a 2005-02-11 devnull running programs
393 d93fca6a 2005-02-11 devnull track them properly. Nonetheless, to keep the database searches efficient
394 d93fca6a 2005-02-11 devnull it is necessary to run
395 d93fca6a 2005-02-11 devnull .I ndbmkhash
396 d93fca6a 2005-02-11 devnull whenever the files are modified.
397 d93fca6a 2005-02-11 devnull It may be profitable to control this by a frequent
398 d32deab1 2020-08-16 rsc .MR cron (8)
401 d93fca6a 2005-02-11 devnull .I Ndbmkhosts
402 d93fca6a 2005-02-11 devnull generates a BSD style
403 d93fca6a 2005-02-11 devnull .BR hosts ,
404 d93fca6a 2005-02-11 devnull .BR hosts.txt ,
406 d93fca6a 2005-02-11 devnull .B hosts.equiv
407 d93fca6a 2005-02-11 devnull files from ndb data base files specified on the
408 d93fca6a 2005-02-11 devnull command line (default
409 d93fca6a 2005-02-11 devnull .B \*9/ndb/local
411 d93fca6a 2005-02-11 devnull .BR \*9/ndb/friends ).
412 d93fca6a 2005-02-11 devnull It only processes hosts whose domain names end in
413 d93fca6a 2005-02-11 devnull .IR domname .
414 d93fca6a 2005-02-11 devnull The output files are named
415 d93fca6a 2005-02-11 devnull .BI db. domname \fR,
416 d93fca6a 2005-02-11 devnull .BI equiv. domname \fR,
418 d93fca6a 2005-02-11 devnull .BI txt. domname \fR.
419 d93fca6a 2005-02-11 devnull For historical reasons, the default
420 d93fca6a 2005-02-11 devnull .I domname
422 d93fca6a 2005-02-11 devnull .BR research.att.com.
423 d93fca6a 2005-02-11 devnull .SH EXAMPLE
426 d93fca6a 2005-02-11 devnull % ndbquery sys helix
427 d93fca6a 2005-02-11 devnull sys=helix dom=helix.research.bell-labs.com bootf=/mips/9powerboot
428 d93fca6a 2005-02-11 devnull ip=135.104.117.31 ether=080069020427
429 d93fca6a 2005-02-11 devnull proto=il
431 d93fca6a 2005-02-11 devnull .SH FILES
433 d93fca6a 2005-02-11 devnull .B \*9/ndb/local
434 d93fca6a 2005-02-11 devnull first database file searched
436 d93fca6a 2005-02-11 devnull .B \*9/ndb/local.*
437 d93fca6a 2005-02-11 devnull hash files for
438 d93fca6a 2005-02-11 devnull .B \*9/ndb/local
439 d93fca6a 2005-02-11 devnull .SH SOURCE
440 d93fca6a 2005-02-11 devnull .B \*9/src/cmd/ndb
441 d93fca6a 2005-02-11 devnull .SH SEE ALSO
442 d32deab1 2020-08-16 rsc .MR ndb (3) ,
