Resource Records For Listservs

[Richard Johnsson]

> Delivery-Date: Wed, 27 Dec 2000 18:25:42 -0800
> Return-Path: <bind-users-bounce at isc.org>
> Received: from pub3.rc.vix.com (pub3.rc.vix.com [204.152.186.34]) by
hamilton.com with ESMTP id eBS2Pd600533; Wed, 27 Dec 2000 18:25:40 -0800 (PST)
> Received: from pub3.rc.vix.com (pub3.rc.vix.com [204.152.186.34])
> 	by pub3.rc.vix.com (Postfix) with ESMTP
> 	id DC6193E56; Wed, 27 Dec 2000 18:25:22 -0800 (PST)
> Received: with LISTAR (v1.0.0; list bind-users); Wed, 27 Dec 2000
18:24:20 -0800 (PST)
> Received: from isrv3.isc.org (isrv3.isc.org [204.152.184.87])
> 	by pub3.rc.vix.com (Postfix) with ESMTP id 65E7C3E25
> 	for <bind-users at pub3.rc.vix.com>; Wed, 27 Dec 2000 18:24:18 -0800 (PST)
> Received: from fw1-b.osis.gov (fw1-b.osis.gov [204.178.104.234]) 
> 	by isrv3.isc.org (8.11.0/8.9.1) via SMTP id eBS2OHY27374
> 	for <bind-users at isc.org>; Wed, 27 Dec 2000 18:24:17 -0800 (PST)
> 	env-from (jsdy at cospo.osis.gov)
> Received: from washington.cospo.osis.gov by fw1-b.osis.gov with SMTP id
VAA03453
>   (InterLock SMTP Gateway 3.0 for <bind-users at isc.org>);
>   Wed, 27 Dec 2000 21:24:15 -0500
> Received: (from jsdy at localhost) by washington.cospo.osis.gov (8.8.6
(PHNE_14041)/8.7.1-cospo) id VAA20307; Wed, 27 Dec 2000 21:24:15 -0500 (EST)
> Date: Wed, 27 Dec 2000 21:24:15 -0500
> From: Joseph S D Yao <jsdy at cospo.osis.gov>
> To: "Robert L. Cochran Jr." <cochranb at clark.net>
> Cc: bind-users at isc.org
> Subject: Re: Resource Records For Listservs
> Message-Id: <20001227212415.L17224 at washington.cospo.osis.gov>
> Mail-Followup-To: "Robert L. Cochran Jr." <cochranb at clark.net>,
> 	bind-users at isc.org
> References: <000e01c06f98$b2a5db20$9e0c8fa8 at bobc>
> Mime-Version: 1.0
> Content-type: text/plain; charset=us-ascii
> X-Mailer: Mutt 1.0i
> In-Reply-To: <000e01c06f98$b2a5db20$9e0c8fa8 at bobc>; from
cochranb at clark.net on Tue, Dec 26, 2000 at 07:05:18PM -0500
> X-DCC-MAPS-Metrics: isrv3.isc.org 101; IP=0/1 env_From=0/2 From=0/4
Subject=0/1
> 	Message-ID=0/1 Received=0/1 Body=0/1 Fuz1=0/1
> Content-Transfer-Encoding: 8bit
> Sender: bind-users-bounce at isc.org
> Errors-To: bind-users-bounce at isc.org
> Precedence: bulk
> List-unsubscribe: <mailto:bind-users-request at isc.org?Subject=unsubscribe>
> X-List-ID: <bind-users.isc.org>
> 
> 
> On Tue, Dec 26, 2000 at 07:05:18PM -0500, Robert L. Cochran Jr. wrote:
> > 
> > Hello, I am working on setting up a listserv by using the LISTSERV-LITE
> > product from http://www.lsoft.com . I remember seeing another domain's zone
> > records and I think one of these was an 'A' record with the label
> > 'listserv'. Is there a good reason for adding details pertinent to a
> > listserv to my zone data?
> > 
> > Thanks
> > 
> > Bob Cochran
> 
> As lsoft.com no doubt TRIED to make you aware, the name "Listserv" is a
> trademark of theirs for the mailing-list software that they sell.  The
> generic name is mailing list.  There is no such thing as "a listserv".
> 
> Your mailing-list server, presumably but not necessarily also your mail
> server, may have any name that you want.  It can also have aliases,
> using CNAME records.  I tend to have "mail" as one of the aliases for
> my mail server, because (a) anyone can tell what it is from the MX
> record anyway, and (b) it helps to have a name that can travel with the
> service if it moves from machine to machine [which it does at long
> intervals].
> 
> There are arguments for and against giving machines names related to
> their functions.  For: primarily the clarity that it brings to those
> trying to figure out where your servers are (presumably new users and
> new admins).  Also (b) above.  Against: primarily the clarity that it
> brings to those trying to figure out where your servers are (presumably
> hackers/crackers).  Plus the fact that services may be moved to another
> machine.  Also the aesthetics of naming your 7 computers after the 7
> Dwarves, or something like that.  ;-)
> 
> It is your job to assess the benefits versus the risks of appropriately
> naming your mailing-list machine.
> 
> -- 
> Joe Yao				jsdy at cospo.osis.gov - Joseph S. D. Yao
> COSPO/OSIS Computer Support					EMT-B
> -----------------------------------------------------------------------
> This message is not an official statement of COSPO policies.
> 
>