Configuring Systems for Terminals, Printers, and Other Serial Devices (32022-90057)

RAFCP Theory of Operation
DNS Requirements
Appendix D
214
DNS Requirements
DNS contains the core information to resolve RAFCP addressing. There are 2 entries for
each MPE/iX accessed using RAFCP: a Well Known Service (WKS) record which
contains the IP address of the FEDTC and a protocol number referring to UDP; a TeXT
(TXT) record which contains the Node name of the MPE/iX host. This name must be the
same as the one entered under NMMGR on the host. There is one entry for the RDTC
accessed by the FEDTC using RAFCP. It consists of an Address (A) record which
contains the IP address of the RDTC. The RDTC name is the Node name configured on
OpenVeiw DTC Manager of the RDTC. The ARPA domain is the one of the FEDTC.
NOTE An MPE/iX host and a RDTC must always be configured in the DNS to access the same
FEDTC. Not doing this may prevent packets of the MPE/iX host (belonging to the same
AFCP connection) from being forwarded correctly by the FEDTC.
NOTE The DNS standard does not allow the use of underscores "_" in ARPA names. HP Node
name may contain underscores "_". A DTC Node name configured in NNMGR or in the
OpenView DTC Manager must not contain underscores "_". These names are resolved
using DNS.
When users type the DTC connect command, they don't specify the ARPA domain
corresponding to the FEDTC they access. If they don't specify one, the ARPA domain of
the RDTC will be used to interrogate DNS. DNS must be configured accordingly.