Path: utzoo!attcan!uunet!husc6!bloom-beacon!apple!bionet!lear From: lear@NET.BIO.NET (Eliot Lear) Newsgroups: comp.mail.uucp Subject: Re: Grumpy != grumpy Message-ID: Date: 15 Nov 88 22:30:07 GMT References: <398@ditka.UUCP> <42300005@uicsrd.csrd.uiuc.edu> <1689@edison.GE.COM> <12881@ncoast.UUCP> <1988Nov14.115706.11635@ateng.ateng.com> Organization: Natl Computer Resource for Mol. Biology Lines: 26 To: chip@ateng.ateng.com Chip Salzenberg writes: > I disagree. If UUCP is being used, you (the sender) still have to know how > to get to the *gateway* for the destination domain! WElllllll....... There are two problems here, Chip. First, be careful to understand that domains don't have to have gateways, but they do have to have name servers. An illustrative example: Introducing FOO.COM, a multinational enterprise that has offices everywhere you can think of. I want to mail to XYZ.FOO.COM, a branch located in Mountain View. The name server for FOO.COM, located in Tarytown, NY hands me back an MX record saying send it to AMES.ARC.NASA.GOV, located 10 blocks from me. So really what we need is a way for uucp sites to have access to name servers. Yes, this would require extensions to UUCP. However, we are talking near term so such a software solution should not be out of the question. (Can you say DIAL-A-DOMAIN? ;-) Also, keep in mind that one of goals of DNS is to AVOID tables for other sites. A software solution should reflect that theme. -- Eliot Lear [lear@net.bio.net]