Technical data

Index
A
Access control, 1–5
and the NFS client, 20–6
superuser privileges and NFS, 20–5
using the proxy database and system privileges,
20–6
Accounts
setting up for local and remote users, 1–5
Acronyms, D–1 to D–3
ADDRESS.DB
BIND server databases, 5–30
Address mapping, 4–10
Address Resolution Protocol (ARP)
see ARP
ADFs
and non-STREAM_LF files, 21–2
creating customized, 21–3
record handling for the NFS client, 21–2
using NFS client defaults, 21–2
Alias file
creating, for SMTP, 17–7
Allocating addresses
for DHCP clients, 7–2
ANALYZE CONTAINER command, 20–15
Analyzing
container file systems, 20–15
SMTP queues, 17–6
Anonymous FTP, 15–2
configuring, 15–1
ARP
address mapping, 4–10
cache timeout, 7–46
proxy, 3–13
AS2EB macro, B–1
Assigning routing preferences, A–5
Attribute description files
see ADFs, 21–2
Authenticating users
for network printing, 22–10
Authentication
NFS client
mapping user identities, 21–4
NTP, 12–13
of NFS clients, 20–16
PC-NFS, 24–2
Authentication (cont’d)
remote commands, 16–1
Authentication traps
enabling, 13–23
Automounting, 21–10
Autonomous system
specifying, in GATED configuraton, A–15
Auxiliary server, 1–7
activating event logging, 1–10
configuring, 1–8
create process, 1–7
description of, 1–7
handling incoming requests, 1–7
initializing services, 1–9
rejecting client requests, 1–8
SMTP startup, 17–1
B
Background mounting, 21–10
Backup time server
NTP setup, 12–9
Berkeley Internet Name Domain (BIND)
see BIND, BIND server, BIND resolver
name server, 5–1
common configurations, 5–2
defined, 5–2
resolver
defined, 5–2
BGP, 4–2
overview, A–17
BIND resolver, 5–33 to 5–34
changing default configuration, 5–34
configuring, 5–33
example configurations, 5–34
lookups, 5–33
BIND server, 5–5 to 5–31
backing up zone data, 5–27
configuration statements, 5–5
configuration template, 5–5
configuring, 5–5
cache-only servers, 5–32
forwarders, 5–32
master servers, 5–32
slave servers, 5–32
converting UCX V4.x configuration, 5–31
converting UNIX databases, 5–25
databases
Index–1