7-4 Netra Internet Server 3.1 User’s Manual—September 1996
7
Configuration Options
When configuring each name service, you must take into account both the
client side and the server side.
Local Name Service
For the Local name service, the Netra server is both client and server. As a local
name server, your Netra server will contain a list of host-name-to-host-address
mappings for its own use. These mappings are only available to applications
running on the Netra server. Information entered in the local database is
automatically available to programs running locally.
NIS
For the NIS name service, you can only configure the client side. You cannot
configure an NIS server to run on the Netra server. This means that an NIS
server should already be running on another host.
DNS
For the DNS name service, you can configure a client and a server.
• When a Netra server functions as a DNS client, it does not perform any
name service functions. If you want the Netra server to be a DNS client, you
should already have name servers for your DNS domain. You can choose a
DNS server that is running either on another machine or on the Netra
server. You can also configure alternate servers that will be used when the
first server is unavailable.
• The Netra server can be configured as a DNS server. All DNS servers cache
the results of name service queries. This means that repeat queries are
answered by the local name server rather than the original name server
(until the information is out of date). When a DNS server is not configured
with any primary or secondary domains, it is called a cache-only server.
As a primary domain server, the Netra server maintains a master database for
its own domain. (You must make all updates to the DNS database.) The
primary name server regularly propagates information to the other name
servers in its domain. It should have a secondary name server to back it up,
either on your LAN or at your ISP.
To Next Page
Loading...
