Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!ucsd!ucbvax!TRANSARC.COM!Craig_Everhart From: Craig_Everhart@TRANSARC.COM Newsgroups: comp.protocols.tcp-ip.domains Subject: Re: Philosophical question Message-ID: Date: 23 Oct 90 19:12:51 GMT References: <9010231539.AA06606@quetzalcoatl.erg.sri.com> Sender: daemon@ucbvax.BERKELEY.EDU Distribution: inet Organization: The Internet Lines: 19 I've been recommending (to anyone who wants my opinions) that if you send mail with, say, a From: line of foo@bar.baz.ola, then there should be some machine somewhere named bar.baz.ola (yes, with an A record) so that old-timers can still get mail to you. The andrew.cmu.edu setup is a reasonable example. There are three machines advertised via MX as being recipients for andrew.cmu.edu mail, and the andrew.cmu.edu machine itself has the least-favored status in MX-land. (The other two machines, po2.andrew.cmu.edu and po3.andrew.cmu.edu, each are more preferred MX recipients for andrew.cmu.edu. And all mail from the domain goes out as From: local-part@andrew.cmu.edu .) It's been interesting, watching the volume of incoming mail shift, over the years, from the andrew.cmu.edu machine itself to the other two big MX in-vectors. Of course, providing a machine named bar.baz.ola (and an address record) solves not only the problem of non-MX mailers, but also the problem of where to connect for FTP and finger and other services. Craig