Path: utzoo!attcan!uunet!lll-winken!ames!pasteur!agate!bionet!csd4.milw.wisc.edu!nic.MR.NET!hal!ncoast!allbery From: allbery@ncoast.ORG (Brandon S. Allbery) Newsgroups: comp.mail.sendmail Subject: Name server service for UUCP sites: an idea Message-ID: <13364@ncoast.ORG> Date: 25 Jan 89 04:18:44 GMT Reply-To: allbery@ncoast.ORG (Brandon S. Allbery) Organization: Cleveland Public Access UN*X, Cleveland, Oh Lines: 26 I recently had the thought that if the lists of systems known to Internet nameservers (and the paths, at least to the forwarders) was posted occasionally, UUCP sites could then collect the information and add it to the maps -- and pathalias could then properly deal with the Internet. (Think of it as a more advanced version of "arpatxt".) Of course, this is conditional, based on the assumption that it's possible to make such a list in a rational way; not being all that familiar with nameservers and their associated alphabet soup (you know: A, CNAME, MX, etc. ;-) I don't know if it can be done. If it can, this would in effect provide a map of Internet connections, so that pathalias can generate better paths to Internet sites (e.g. it'll stop telling me that uunet is at hal!cwjcc!gatech!...!uunet when hal!uunet.uu.net is faster (5 minutes to an hour, maximum!). It might be preferred to leave off sites which are only on the Internet via a forwarder (e.g. ncoast, or any of the .US sites), and RFC822 dictates that some way be found to prevent mail paths from "hitching a ride" on the Internet to travel between two non-Internet sites. Any thoughts from the mail gurus? ++Brandon -- Brandon S. Allbery, moderator of comp.sources.misc allbery@ncoast.org uunet!hal.cwru.edu!ncoast!allbery ncoast!allbery@hal.cwru.edu Send comp.sources.misc submissions to comp-sources-misc@ NCoast Public Access UN*X - (216) 781-6201, 300/1200/2400 baud, login: makeuser