Xref: utzoo comp.protocols.tcp-ip:9151 comp.mail.misc:2572
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucsd!brian
From: brian@ucsd.Edu (Brian Kantor)
Newsgroups: comp.protocols.tcp-ip,comp.mail.misc
Subject: Re: MXing the world
Message-ID: <10115@ucsd.Edu>
Date: 10 Nov 89 00:14:10 GMT
References: <8911051717.AA10735@alw.nih.gov> <2441@csun.edu> <4902@yunexus.UUCP>
Reply-To: brian@ucsd.edu (Brian Kantor)
Followup-To: comp.protocols.tcp-ip
Organization: The Avant-Garde of the Now, Ltd.
Lines: 24

I have in MY nameserver the following for the bitnet "top level
domain".  Because there is no record in the root nameserver pointing at
me for ".bitnet", this is not advertised to the outside world, but it
allows my mail system to treat "user@host.bitnet" just as it would any
other domain-type mail.  Because I assign these hosts equal priority
(and because sendmail-5.61 randomizes usage of equal-priority MXs), my
limited amount of bitnet traffic gets spread between the several
gateways I have listed.  (I think there are more internet->bitnet mail
gateways but these are the ones I know about.)

This is a real hack but it works real well for me.  I don't see why
this couldn`t be done internet-wide but I suspect the reason is other
than technical.  Is that true?
	- Brian

in the boot file:
	primary	bitnet bitnet

in the 'bitnet' file:
	@		IN	SOA	ucsd.EDU. brian.ucsd.EDU. (
			880506 7200 1800 2419200 86400 )
	*		IN	MX	10 cunyvm.cuny.edu.
	*		IN	MX	10 mitvma.mit.edu.
	*		IN	MX	10 uicvm.uic.edu.