Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"INFO-PMDF@YMIR.CLAREMONT.EDU"
Date:         Wed, 8 Apr 92 14:14:00 PST
From:         John W Manly <JWMANLY@AMHERST.EDU>
Subject:      When should one use a local host aliases in PMDF.CNF?
X-To:         INFO-PMDF@YMIR
Newsgroups: bit.listserv.pmdf-l

Hi there.

I have a question about the recommended method for setting up PMDF
configuration files.  Specifically, the PMDF System Manager's Guide,
section 3.2.5.4, says that the use of the local-host-alias (the second
token on the second line of a channel block) is discouraged.

Here at Amherst College, our VAX is connected to both BITNET and the Internet.
Our configuration file looks like this (shortened for brevity):
---------------------------------------------------------------------------
AMHERST                 $U@amherst
AMHERST.BITNET          $U@amherst
AMHERST.EDU             $U@amherst.edu
AMH.AMHERST.EDU         $U@amherst.edu
!
AMHERST.EDU            $U%$H$D@mtcp-daemon
!
MITVMA2                 $U%$H@jnet-daemon
MITVMA2.BITNET          $U%$H@jnet-daemon
!
DNET                   $U%$H@decnet-mail
!
<PMDF_ROOT:[table]tcpip.rules
<PMDF_ROOT:[table]gates.rules

l 822 bidirectional nosendpost
AMHERST
AMHERST.EDU

d
DECNET-MAIL

bit_local 733 bidirectional single nosmtp nosendpost
JNET-DAEMON

mtcp_local single_sys smtp nosendpost
MTCP-DAEMON amherst.edu

<PMDF_ROOT:[table]gates.chans
---------------------------------------------------------------------------
Note in particular that our official host name (first name in the L channel
block) is "AMHERST", and that the Multinet TCP/IP channel needs a local-host-
name of "AMHERST.EDU" so that that name will be used when emitting addresses
on Internet.

However, in the spirit of "pick a single name and stick to it", we would  LIKE
for our official host name to be "AMHERST.EDU".  The question is, what then do
we do about all the channel definitions in the GATES.CHANS file?  Presumably we
need to put local-host-aliases in those channels so that the emitted name is
"AMHERST", instead of "AMHERST.EDU", lest some RSCS-only BITNET site be unable
to REPLY to our messages sent out over JNET.

So a) is my assesment of our needing local-host-aliases in these channels
correct, b) if so, how do we get them in there (is that what the bitnet_alias
symbol is for in BITNET_DOMAINS.COM?), c) what do I do about the DECNET-MAIL
channel, and d) have I completley misunderstood the nature of
official-host-names vs local-host-aliases, and is there some better way to
handle all this?

What I'm thinking about is something like the following:
---------------------------------------------------------------------------
AMHERST                 $U@amherst.edu
AMHERST.BITNET          $U@amherst.edu
AMHERST.EDU             $U@amherst.edu
AMH.AMHERST.EDU         $U@amherst.edu
!
AMHERST.EDU            $U%$H$D@mtcp-daemon
!
MITVMA2                 $U%$H@jnet-daemon
MITVMA2.BITNET          $U%$H@jnet-daemon
!
DNET                   $U%$H@decnet-mail
!
<PMDF_ROOT:[table]tcpip.rules
<PMDF_ROOT:[table]gates.rules

l 822 bidirectional nosendpost
AMHERST.EDU

d
DECNET-MAIL

bit_local 733 bidirectional single nosmtp nosendpost
JNET-DAEMON amherst

mtcp_local single_sys smtp nosendpost
MTCP-DAEMON

<PMDF_ROOT:[table]gates.chans
---------------------------------------------------------------------------
Note the "AMHERST" as local-host-alias in the BIT_LOCAL channel, and the
assumption that the GATES.CHANS file would be made with bitnet_alieas
set to "AMHERST" as well.

- John W. Manly  <JWMANLY@AMHERST.EDU>     System Manager -- Amherst College
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU