Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!sri-unix!rutgers!ames!ucbcad!ucbvax!SUN.COM!melohn
From: melohn@SUN.COM (Bill Melohn)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: Mailing to DEC Easynet
Message-ID: <8708120401.AA03055@sluggo.sun.com>
Date: Wed, 12-Aug-87 00:01:03 EDT
Article-I.D.: sluggo.8708120401.AA03055
Posted: Wed Aug 12 00:01:03 1987
Date-Received: Fri, 14-Aug-87 01:26:30 EDT
References: <12325530286.154.A.ERIC@GSB-HOW.Stanford.EDU>
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: sun!melohn (Bill Melohn)
Distribution: world
Organization: Sun Microsystems, Mountain View
Lines: 16

In article <12325530286.154.A.ERIC@GSB-HOW.Stanford.EDU> A.Eric@GSB-HOW.STANFORD.EDU (Eric M. Berg) writes:
>It's helpful to know that DEC Easynet nodes seem to have two different names
>each: a DECnet node name, and an internet-style name.  So, for example, most
>of the Santa Clara office sales people have accounts on "USWRSL.DEC.COM"
>("US Western Region SaLes", as close as I can guess), which is also known
>as "RHEA" (DECnet node name).


This is done (no suprise) by using the domain name server, which has
an MX record defined for all of the valid DECNET node names in the DEC
Enet. From the outside, you should be able to get to any DEC Enet node
by sending to <username>@<dec node name>.dec.com, assuming you run the
nameserver.  The node RHEA is merely a forwarding node in the internal
chain between DECWRL and the rest of the DEC Enet.

Domain names; there not just for IP anymore..