Installation guide

the system supports the Berkeley Internet Name Domain (BIND) service,
the Network Information Service (NIS), and the Network Time Protocol
(NTP) Time Synchronization Protocol (TSP) time services.
The DIGITAL UNIX system does not support the Kerberos authentication
service. You cannot use Kerberos for password security, data encryption, or
authentication services. It also does not support the Hesiod naming service.
This section gives an overview of the BIND, NIS, and NTP services
available on DIGITAL UNIX systems.
As does the ULTRIX system, the DIGITAL UNIX system has an
/etc/svc.conf file that determines how your system uses the BIND and
NIS services to find host information. You can use the svcsetup command
to maintain the svc.conf file. Because the DIGITAL UNIX system does
not include the Hesiod name server, you can specify bind only in the hosts
database entry.
4.15.1 Berkeley Internet Domain Service
Like an ULTRIX system, the DIGITAL UNIX system has the Berkeley
Internet Name Domain (BIND) service. However, the BIND service on
DIGITAL UNIX does not include the Hesiod name server. Because
DIGITAL UNIX systems do not support the Hesiod naming service, you
cannot use the BIND service to distribute the following databases on a
DIGITAL UNIX system:
• aliases
• group
• networks
• passwd
• protocols
• rpc
• services
You can use the Network Information Service (NIS) to distribute these
databases. See Section 4.15.2 for information about NIS.
Like the ULTRIX BIND service, the DIGITAL UNIX BIND service is based
on a server/client model. Servers maintain databases of host names and
addresses. When client systems require information about a host, they
query the resolver file, resolv.conf, for the IP address of a BIND server
to service their request. The BIND server runs a daemon, named, that
services the client’s requests.
Overview of DIGITAL UNIX System and Network Administration 4–23