Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!ucsd!hub.ucsb.edu!spectrum.CMC.COM!lars From: lars@spectrum.CMC.COM (Lars Poulsen) Newsgroups: comp.protocols.tcp-ip.domains Subject: Re: Clarification Re: .de (was: Domains created in June 1990) Message-ID: <1990Aug18.053952.931@spectrum.CMC.COM> Date: 18 Aug 90 05:39:52 GMT References: <2152@unido.UUCP> <3686@ruuinf.cs.ruu.nl> Distribution: comp Organization: Rockwell CMC Lines: 24 In article <3686@ruuinf.cs.ruu.nl> henkp@ruuinf.cs.ruu.nl (Henk P. Penning) writes: >> ... Could somebody explain why mail to (fi) uni-mainz.de >> gets MX'ed to cunyvm.cuny.edu (that's in New York I think). In article a0020@rrz.uni-koeln.de (Axel Clauberg) writes: >I think mail to Mainz is delivered via Bitnet, not SMTP(IP). As MXes are >global you have to make some compromises... >A european gateway might be better for europeans, but not for the "rest >of the world". I do not have the inclination to actually *try* this, but since BITNET is such a common interconnect problem, would it not be best to (1) Define INTERBIT.BIT.NET as CNAME CUNYVM.CUNY.EDU "officially"/"globally" (2) Define the BITNET hosts as MX INTERBIT.BIT.NET (3) Allow each regional or local nameserver to define in its cache preload INTERBIT.BIT.NET CNAME (some nearby BIT/Inter gateway) Would this not solve the problem ? -- / Lars Poulsen, SMTS Software Engineer CMC Rockwell lars@CMC.COM