3 ndbquery, ndbmkhash, ndbmkdb, ndbipquery, ndbmkhosts \- network database
24 The network database holds administrative information used by
32 searches the database for an attribute of type
38 is not specified, all entries matched by the search are returned.
41 is specified, the value of the first pair with attribute
43 of all the matched entries is returned.
50 to search for the values of the attributes
52 corresponding to the system
53 with entries of attribute type
60 creates a hash file for all entries with attribute
64 The hash files are used by
66 and by the ndb library routines.
69 .\" is a server used by
71 .\" to translate network names.
72 .\" It is started at boot time.
73 .\" It finds out what networks are configured
77 .\" It can also be told about networks by writing
80 .\" a message of the form:
82 .\" .B "add net1 net2 ..."
85 .\" also sets the system name in
87 .\" if it can figure it out.
91 .\" supplies the name of the data base file to use,
93 .\" .BR /lib/ndb/local .
96 .\" specifies the mount point of the
100 .\" causes cs to do nothing but set the system name.
103 .\" can be used to query
105 .\" to see how it resolves addresses.
107 .\" prompts for addresses and prints out what
117 .\" prints their translations and immediately exits.
118 .\" The exit status will be nil only if all addresses
119 .\" were successfully translated
122 .\" flag sets exit status without printing any results.
125 .\" is a server used by
127 .\" and by remote systems to translate Internet domain names.
129 .\" is started at boot time.
132 .\" serves only requests written to
137 .\" supplies the name of the data base file to use,
139 .\" .BR /lib/ndb/local .
142 .\" specifies the mount point of the
146 .\" also answer domain requests sent to UDP port 53.
149 .\" whenever a zone that we serve changes, send UDP NOTIFY
150 .\" messages to any dns slaves for that zone.
153 .\" whenever we receive a UDP NOTIFY message, run
155 .\" with the domain name of the area as its argument.
158 .\" defer to other servers to resolve queries.
162 .\" option is specified, the servers used come from the
164 .\" attribute in the database. For example, to specify a set of dns servers that
165 .\" will resolve requests for systems on the network
169 .\" ipnet=mh-net ip=135.104.0.0 ipmask=255.255.0.0
170 .\" dns=ns1.cs.bell-labs.com
171 .\" dns=ns2.cs.bell-labs.com
172 .\" dom=ns1.cs.bell-labs.com ip=135.104.1.11
173 .\" dom=ns2.cs.bell-labs.com ip=135.104.1.12
177 .\" The server for a domain is indicated by a database entry containing
183 .\" For example, the entry for the Internet root is:
187 .\" ns=A.ROOT-SERVERS.NET
188 .\" ns=B.ROOT-SERVERS.NET
189 .\" ns=C.ROOT-SERVERS.NET
190 .\" dom=A.ROOT-SERVERS.NET ip=198.41.0.4
191 .\" dom=B.ROOT-SERVERS.NET ip=128.9.0.107
192 .\" dom=C.ROOT-SERVERS.NET ip=192.33.4.12
195 .\" The last three lines provide a mapping for the
196 .\" server names to their ip addresses. This is only
197 .\" a hint and will be superseded from whatever is learned
198 .\" from servers owning the domain.
200 .\" You can also serve a subtree of the domain name space from the local
201 .\" database. You indicate subtrees that you'ld like to serve by
204 .\" attribute to the root entry.
205 .\" For example, the Bell Labs CS research domain is:
208 .\" dom=cs.bell-labs.com soa=
209 .\" refresh=3600 ttl=3600
210 .\" ns=plan9.bell-labs.com
211 .\" ns=ns1.cs.bell-labs.com
212 .\" ns=ns2.cs.bell-labs.com
213 .\" mb=presotto@plan9.bell-labs.com
214 .\" mx=mail.research.bell-labs.com pref=20
215 .\" mx=plan9.bell-labs.com pref=10
216 .\" dnsslave=nslocum.cs.bell-labs.com
217 .\" dnsslave=vex.cs.bell-labs.com
222 .\" entry is the mail address of the person responsible for the
224 .\" .BR postmaster ).
227 .\" entries list mail exchangers for the domain name and
231 .\" define the area refresh interval and the minimum TTL for
232 .\" records in this domain.
235 .\" entries specify slave DNS servers that should be notified
236 .\" when the domain changes. The notification also requires
241 .\" You can also serve reverse lookups (returning the name that
242 .\" goes with an IP address) by adding an
244 .\" attribute to the entry defining the root of the reverse space.
245 .\" For example, to provide reverse lookup for all addresses in
246 .\" starting with 135.104 you must have a record like:
249 .\" dom=104.135.in-addr.arpa soa=
250 .\" refresh=3600 ttl=3600
251 .\" ns=plan9.bell-labs.com
252 .\" ns=ns1.cs.bell-labs.com
253 .\" ns=ns2.cs.bell-labs.com
255 .\" Notice the form of the reverse address, i.e., it's the bytes of the
256 .\" address range you are serving reversed and with
258 .\" appended. This is a standard form for a domain name in an IPv4 PTR record.
260 .\" If such an entry exists in the database, reverse addresses will
261 .\" automaticly be generated from any IP addresses in the database
262 .\" that are under this root. For example
265 .\" dom=ns1.cs.bell-labs.com ip=135.104.1.11
267 .\" will automaticly create both forward and reverse entries for
268 .\" .B ns1.cs.bell-labs.com .
269 .\" Unlike other DNS servers, there's no way to generate
270 .\" inconsistent forward and reverse entries.
272 .\" Delegation of a further subtree to another set of name servers
273 .\" is indicated by an
278 .\" dom=bignose.cs.research.bell-labs.com
280 .\" ns=anna.cs.research.bell-labs.com
281 .\" ns=dj.cs.research.bell-labs.com
284 .\" Nameservers within the delegated domain (as in this example)
285 .\" must have their IP addresses listed elsewhere in
289 .\" Wild-carded domain names can also be used.
290 .\" For example, to specify a mail forwarder for all Bell Labs research systems:
293 .\" dom=*.research.bell-labs.com
294 .\" mx=research.bell-labs.com
297 .\" `Cname' aliases may be established by adding a
299 .\" attribute giving the real domain name;
300 .\" the name attached to the
302 .\" attribute is the alias.
303 .\" `Cname' aliases are severely restricted;
304 .\" the aliases may have no other attributes than
306 .\" and are daily further restricted in their use by new RFCs.
309 .\" cname=anna.cs.research.bell-labs.com dom=www.cs.research.bell-labs.com
313 .\" can be used to query
315 .\" to see how it resolves requests.
317 .\" prompts for commands of the form
319 .\" .I "domain-name request-type"
329 .\" In the case of the inverse query type,
332 .\" will reverse the ip address and tack on the
339 .\" but bypasses the local server.
340 .\" It communicates via UDP with the domain name servers
341 .\" in the same way that the local resolver would and displays
342 .\" all packets received.
343 .\" The query can be specified on the command line or
344 .\" can be prompted for.
345 .\" The queries look like those of
347 .\" with one addition.
349 .\" can be directed to query a particular name server by
351 .\" .BI @ name-server\f1.
352 .\" From that point on, all queries go to that name server
353 .\" rather than being resolved by
357 .\" command returns query resolution to
359 .\" Finally, any command preceded by a
360 .\" .BI @ name-server
361 .\" sets the name server only for that command.
367 .\" interface and the database file
368 .\" .BR /lib/ndb/local.
376 .\" .B /lib/ndb/external
380 .\" option is the same as for
384 is used in concert with
387 uucp systems files and IP host files
389 It is very specific to the situation at Murray Hill.
391 When the database files change underfoot,
393 track them properly. Nonetheless, to keep the database searches efficient
394 it is necessary to run
396 whenever the files are modified.
397 It may be profitable to control this by a frequent
402 generates a BSD style
407 files from ndb data base files specified on the
408 command line (default
411 .BR \*9/ndb/friends ).
412 It only processes hosts whose domain names end in
414 The output files are named
416 .BI equiv. domname \fR,
418 .BI txt. domname \fR.
419 For historical reasons, the default
422 .BR research.att.com.
427 sys=helix dom=helix.research.bell-labs.com bootf=/mips/9powerboot
428 ip=135.104.117.31 ether=080069020427
434 first database file searched
