BIND Servers and Clients

BIND Servers and Clients

BIND is based on a server-client relationship. There are several different classes of servers, with varying degrees of authority. This section discusses the interaction between various types of servers, and between servers and clients. This information is summarized in Table 6-1.

Table 6-1 summarizes the general characteristics for various BIND server configurations.

BIND Server Configurations
Primary Server Secondary Server Caching-only Server Forwarder Server Slave Server
Authoritative server for the domain "Delegated" authority from primary server Non- authoritative Non- authoritative Non- authoritative
Loads data from local file Loads data from primary server Answers queries or forwards queries to authoritative servers Answers recursive requests or interacts with other name servers before answering requests Accesses data from specified list of servers (forwarders)

BIND Server Configurations
Primary Server	Secondary Server	Caching-only Server	Forwarder Server	Slave Server
Authoritative server for the domain	"Delegated" authority from primary server	Non- authoritative	Non- authoritative	Non- authoritative
Loads data from local file	Loads data from primary server	Answers queries or forwards queries to authoritative servers	Answers recursive requests or interacts with other name servers before answering requests	Accesses data from specified list of servers (forwarders)

All server configurations must run the named server daemon. The named daemon is started automatically during station startup if the configuration flag named is "on." See the chkconfig(1M) reference page for more details.

The client accesses data from the name servers specified in its resolv.conf file. It does not run the domain server, named.

Master Servers
Slave and Forwarding Servers
Caching-Only Server
Clients