Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!b-tech!zeeff From: zeeff@b-tech.ann-arbor.mi.us (Jon Zeeff) Newsgroups: comp.protocols.tcp-ip Subject: Re: MXing the world Message-ID: <1989Nov15.165637.6862@b-tech.ann-arbor.mi.us> Date: 15 Nov 89 16:56:37 GMT References: <2029@cmx.npac.syr.edu> <16300008@uxh.cso.uiuc.edu> <4118@phri.UUCP> Reply-To: zeeff@b-tech.ann-arbor.mi.us (Jon Zeeff) Organization: Branch Technology, Ann Arbor, MI Lines: 30 In article <4118@phri.UUCP> roy@phri.UUCP (Roy Smith) writes: > > But what if it did? Let's say I'm the DNS server for the .BITNET >domain. When a request comes in for an MX, I take a look at where the >request came from and use that information to select the proper MX record >to send back. If I can't figure out which is the best, I send back some >default gateway. I'd like to see something similar for uucp sites. Let's say we create a domain foo.org and allow uucp sites to call themselves uucp_name.foo.org (without the problem of having to find a forwarder). When a MX request comes in, we look up the closest internet site based on pathalias data and a list of internet/uucp gateways and respond with this. Make sure that the list of internet/uucp gateways is large wrt to the number of uucp sites using foo.org to prevent load problems. You could do this right now, except for the fact that these internet/uucp gateways need to rewrite the address from uucp_name.foo.org to uucp_name. Too bad sendmail isn't a bit smarter about using some other means of address resolution when it ends up talking to itself (or the DNS having some address rewriting ability). There is currently a problem with uucp sites not getting domain names because they don't have any contacts with forwarders and don't want to pay for something like uunet. They still use the forwarders (by things like user%site@forwarder.domain); it just makes for ugly addresses. -- Branch Technology