![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to build.me CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [CSRG BSD Unix] / 43BSDReno / share / doc / smm / 11.named|
Return to build.me CVS log | Up to [CSRG BSD Unix] / 43BSDReno / share / doc / smm / 11.named |
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: .\" @(#)build.me 6.3 (Berkeley) 9/19/89
12: .\"
13: .sh 1 "Building A System with a Name Server"
14: .pp
15: BIND is comprised of two parts. One is the user interface called the
16: \fIresolver\fP
17: which consists of a group of routines that reside in the C library
18: \fI/lib/libc.a\fP.
19: Second is the actual server called \fInamed\fP.
20: This is a daemon that runs in the background and services queries on a
21: given network port. The standard port for UDP and TCP is specified in
22: \fI/\|etc/\|services\fP.
23: .sh 2 "Resolver Routines in libc"
24: .pp
25: When building your 4.3BSD system you may either
26: build the C library to use the name server resolver routines
27: or use the host table lookup routines to do host name and address resolution.
28: The default resolver for 4.3BSD uses the name server.
29: .pp
30: Building the C library to use the name server changes the way
31: \fIgethostbyname\fP\|(3N), \fIgethostbyaddr\fP\|(3N), and \fIsethostent\fP\|(3N)
32: do their functions.
33: The name server renders \fIgethostent\fP\|(3N) obsolete,
34: since it has no concept of a next line in the database.
35: These library calls are built with the resolver routines needed
36: to query the name server.
37: .pp
38: The \fIresolver\fP is comprised of a few routines that build query
39: packets and exchange them with the name server.
40: .pp
41: Before building the C library, set the variable \fIHOSTLOOKUP\fP
42: equal to \fInamed\fP in \fI/\|usr/\|src/\|lib/\|libc/\|Makefile\fP.
43: You then make and install the C library and compiler and then
44: compile the rest of the 4.3BSD system. For more information
45: see section 6.6 of ``Installing and Operating 4.3BSD on the VAX\(dd''.
46: .(f
47: \(ddVAX is a Trademark of Digital Equipment Corporation
48: .)f
49:
50: .sh 2 "The Name Service"
51: .pp
52: The basic function of the name server is to provide information about network
53: objects by answering queries. The specifications for this name server
54: are defined in RFC1034, RFC1035 and RFC974.
55: These documents can be found in \fI/usr/src/etc/named/doc\fP in 4.3BSD
56: or \fIftp\fPed from nic.ddn.mil. It is also recommeded that
57: you read the related
58: manual pages, \fInamed\fP\|(8),
59: \fIresolver\fP\|(3),
60: and \fIresolver\fP\|(5).
61: .pp
62: The advantage of using a name server over the host table lookup for
63: host name resolution is to avoid the need
64: for a single centralized clearinghouse for all names.
65: The authority for this information can be delegated
66: to the different organizations on the network responsible for it.
67: .pp
68: The host table lookup routines require that the master file
69: for the entire network be maintained at a central location by a few people.
70: This works fine for small networks where there are only a few machines and the
71: different organizations responsible for them cooperate.
72: But this does not work well for large networks where machines
73: cross organizational boundaries.
74: .pp
75: With the name server, the network can be broken into a hierarchy of domains.
76: The name space is organized as a tree according to organizational or
77: administrative boundaries.
78: Each node, called a \fIdomain\fP, is given a label, and the name of the
79: domain is the concatenation of all the labels of the domains from
80: the root to the current domain, listed from right to left separated by dots.
81: A label need only be unique within its domain.
82: The whole space is partitioned into several areas called \fIzones\fP,
83: each starting at a domain and extending down to the leaf domains or to
84: domains where other zones start.
85: Zones usually represent administrative boundaries.
86: An example of a host address for a host at the University of California,
87: Berkeley would look as follows:
88: .(b
89: \fImonet\fP\|\fB.\fP\|\fIBerkeley\fP\|\fB.\fP\|\fIEDU\fP
90: .)b
91: The top level domain for educational organizations is EDU;
92: Berkeley is a subdomain of EDU and monet is the name of the host.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.