Received: from localhost (daemon@localhost) by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id OAA09106; Tue, 15 Oct 1996 14:18:13 -0400 Received: by CS.UTK.EDU (bulk_mailer v1.7); Tue, 15 Oct 1996 14:17:49 -0400 Received: from munnari.OZ.AU (munnari.OZ.AU [128.250.1.21]) by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id OAA09021; Tue, 15 Oct 1996 14:16:43 -0400 Received: from mundamutti.cs.mu.OZ.AU by munnari.OZ.AU with SMTP (5.83--+1.3.1+0.56) id SA12660; Wed, 16 Oct 1996 04:16:16 +1000 (from kre@munnari.OZ.AU) To: John Gardiner Myers Cc: drums@cs.utk.edu Subject: Re: CNAME/1123 breakage In-Reply-To: Your message of "Tue, 15 Oct 1996 14:01:35 -0400." Date: Wed, 16 Oct 1996 04:16:09 +1000 Message-Id: <14630.845403369@munnari.OZ.AU> From: Robert Elz Date: Tue, 15 Oct 1996 14:01:35 -0400 (EDT) From: John Gardiner Myers Message-ID: I am not, however, yet convinced that the presumed breakage is that serious. I agree (I don't think it is a serious issue at all, if it is ever an issue for someone, they can easily replace the CNAME with other DNS data that will work). But I am replying to this message only because of ... Robert Elz writes: > But this only > applies to A records, if the name in the MX is a CNAME, then no A > record is returned, [...] This is an entirely separate issue. We were talking about CNAME's in RCPT commands, not CNAMEs in MX records. RFC 974 recommends against or prohibits this latter practice. (It's not clear to me which) I know, and I thought I said that (explicitly) in the message, I was just responding to someone else who made some comment about doing that as if it was a somehow related issue. kre