Cluster I/O Protocols (CIP) Configuration and Management Manual (H06.16+, J06.05+)

Configure the RESCONF File
The DNR resolves domain names to IP addresses using either DNS or a HOSTS file to provide the
translation. If you did not set the TCP^HOST^FILE or TCP^NODE^FILE parameter, the DNR assumes
it must use DNS. To determine which DNS to use, the DNR interrogates the RESCONF file. Therefore,
you must configure the RESCONF file when using DNS.
The RESCONF file specifies the name of the domain in which the host is running and the IP addresses
of DNS servers to consult. The following example lists three DNS IP addresses (nameserver 127.1,
nameserver 50.0.0.23, and nameserver 50.0.0.36):
domain HP.COM
nameserver 127.1
nameserver 50.0.0.23
nameserver 50.0.0.36
The first server address is the primary server. If that server is unavailable, the resolver contacts the
second server. If the second is unavailable, the resolver tries to contact the third server. Notice that
the first server address is 127.1; this is the address you would use if the current NonStop host had
a server available.
The site update tape (SUT) comes with a sample RESCONF file that is installed into $SYSTEM.ZTCPIP.
The name of this file is SMPLRESC. Modify this file for your environment.
Add the TCPIP^RESOLVER^NAME DEFINE
To override the default RESCONF file, use the environment variable TCPIP^RESOLVER^NAME.
This variable provides flexibility in selecting the RESCONF file accessed for name resolution.
The default RESCONF file is located on $SYSTEM.ZTCPIP. To select a different RESCONF file, use
a TACL ADD DEFINE command like:
ADD DEFINE =tcpip^resolver^name, FILE $data.user.resconf
Customize the NETWORKS File
The NETWORKS file lists the names, numbers, and aliases of networks known to the current host.
This file converts an Internet network address to a symbolic name.
Applications use this file when they call a getnetbyaddr() or a getnetbyname() function. The
NETWORKS file included with the CIP software is a prototype; you should customize this file.
Each entry of the NETWORKS file has this format:
network_name network_number [alias...]
Where network_name is an alphanumeric name, network_number is the assigned network
number, and alias is an alphanumeric name.
The alias is optional for each network, and each network can have more than one alias. The aliases
for each network must be on the same entry line and separated by spaces.
Sample NETWORKS File: SMPLNETW
The site update tape (SUT) comes with a sample NETWORKS filethat is installed into
$SYSTEM.ZTCPIP. The name of this file is SMPLNETW and the contents are shown in the display:
#
# Network configuration file
#
loopback 127
xxx-ether 192.9.200 xxxether ethernet localnet
tdm-oldether 125 tdmoldether
#
# Internet networks
# Internet networks
Configuring CIP 77