*** UNIX MANUAL PAGE BROWSER ***

A Nergahak database for man pages research.

Navigation

Directory Browser

1Browse 4.4BSD4.4BSD
1Browse Digital UNIXDigital UNIX 4.0e
1Browse FreeBSDFreeBSD 14.3
1Browse MINIXMINIX 3.4.0rc6-d5e4fc0
1Browse NetBSDNetBSD 10.1
1Browse OpenBSDOpenBSD 7.7
1Browse UNIX v7Version 7 UNIX
1Browse UNIX v10Version 10 UNIX

Manual Page Search

Manual Page Result

0 Command: named.boot | Section: 4 | Source: Digital UNIX | File: named.boot.4.gz
named.boot(4) Kernel Interfaces Manual named.boot(4) NAME named.boot - named configuration file SYNOPSIS /etc/named.boot DESCRIPTION This file is the default configuration (or boot) file for the named server. The named daemon reads the start-up file when the named daemon starts and when receiving signal SIGHUP. The records in the named.boot file tell the named daemon what type of server it is, which domains (or zones of authority) it has authority over, and where to get the data for initially setting up its database. The name server first needs to know the root name server, which is the authority server for the network. The root name server is established in the named.boot file by specifying the root server filename (named.ca) as the cache for this name server. The general format of each line in this file is as follows: Type Domain Source Determines the type of information required for the database. The Type field can have one of the following values: Indi- cates that the following Domain entry is the name of the default do- main. When the named daemon receives a query with a domain or hostname that does not end with a . (dot), the named daemon appends the default domain name to the queried name. Indicates that the local named server is the primary name server for the domain specified in the Domain field and that the named daemon is to get the data describing the domain from the file specified in the Source field. Indicates that the local named server is a secondary name server for the domain specified in the Do- main field and that the named daemon is to get the data describing the domain from one or more remote primary name servers using the Internet address or addresses specified in the Source field. The named daemon tries each address in the order listed until it successfully receives the data from one of the name servers. Indicates that the local named server is a caching name server for the domain specified in the Domain field and that the named daemon is to get the data describing the do- main from the file specified in the Source field. See named(8) for ad- ditional named.boot file directives. Specifies the domain. Specifies a file containing information that describes the domain. Note that the named daemon does not provide other hosts with the infor- mation contained in a cache file. Cache files are usually used for listing the name servers for domains higher than the local domain. Comments in the boot file begin with a ; (semicolon) and end at the end of the line. These data files can have any name. However, for convenience in main- taining the named database, they are generally given names in the fol- lowing form: /etc/named.extension. The general format of named data files is described in /etc/named.*. EXAMPLES The following examples show the various ways to use the named start-up file. The /etc/named.boot file for venus, a primary name server, con- tains these entries: ; Boot file for primary name server ; ; type domain source file or host domain abc.aus.osf.com cache . /etc/named.ca primary abc.aus.osf.com /etc/named.abcdata primary xyz.aus.osf.com /etc/named.xyzdata primary 201.9.192.in-addr.arpa /etc/named.abcrev primary 100.114.128.in-addr.arpa /etc/named.xyzrev primary 0.0.127.in- addr.arpa /etc/named.local In this example, the primary name server is venus and the Inter- net address is 192.9.201.1. The /etc/named.boot file for kro- nos, a secondary name server, contains these entries: ; Boot file for secondary name server ; ; type domain source file or host domain abc.aus.osf.com cache . /etc/named.ca secondary abc.aus.osf.com 192.9.201.1 192.9.201.2 secondary xyz.aus.osf.com 192.9.201.1 192.9.201.2 secondary 201.9.192.in-addr.arpa 192.9.201.1 192.9.201.2 secondary 100.114.128.in-addr.arpa 192.9.201.1 192.9.201.2 primary 0.0.127.in-addr.arpa /etc/named.local In this example the secondary name server is kronos and the In- ternet address is 192.9.201.2. The /etc/named.boot file for hera, a cache-only name server, contains these entries: ; Boot file for cache only server ; ; type domain source file or host domain abc.aus.osf.com cache . /etc/named.ca primary 0.0.127.in- addr.arpa /etc/named.local RELATED INFORMATION Commands: named(8) Files: named.star(4) delim off named.boot(4)

Navigation Options