Sun Microsystems SunLink SNA 9.1 PU2.1, Руководство по настройке

Страница: 232 / 298

B-6 SunLink SNA 9.1 PU2.1 Server Configuration Guide—August 1997
B
▼
To update the DNS configuration:
1. If you are already running a DNS, install the SunGMAN and register it as
a name server in an existing domain database.
For each system that runs the SunGMAN, the installation procedure adds
the following record to the database of the primary server:
sna IN NS <hostname>
where:
sna is the subdomain representing the SNA resources.
<hostname> is the host running the Sun Name Server.
If you are not running a DNS, go to step 3.
2. Register your Sun SNA domains as subdomains in an existing domain
database. You can add the SNA domains anywhere in your organization’s
or site’s name space.
3. Configure the Sun Name Server by editing the
named.boot
file (the Sun
Name Server’s start-up file) and the
named.db
file. These files are located
in the working directory.
4. If you are already running a DNS, no further configuration is required.
Your client systems are already set up to resolve names using DNS.
If you are not running a DNS, configure your client systems by editing the
/etc/resolv.conf
or
/usr/etc/resolv.conf
file. The
resolv.conf
file
contains two or three of the following directives:
The
domain
directive specifies the default or local domain name. Referring
to Figure B-2, the
resolv.conf
file on the
widget
host would contain the
following domain directive:
domain corp.acme.com
The
nameserver
directive specifies the IP addresses of the local DNS hosts
and must be used if the local DNS does not run on the local host. For
example, to access the name server on hosts 199.97.127.10 and 199.97.127.20,
the
resolv.conf
file would contain the following
nameserver
directive: