From: Greg A. Woods (no email)
Date: Thu Nov 01 2001 - 02:54:11 EST
[ On Thursday, November 1, 2001 at 00:01:54 (-0500), Meng Weng Wong wrote: ]
> Subject: "MX->CNAME considered harmful" considered harmful.
>
> In brief, MX->CNAME is frowned upon because it can cause
> problems under a certain set of circumstances; but when
> those circumstances are easily avoided, does there remain a
> reason to deprecate it?
Unless you're prepared to fix some other RFCs then you can't get rid of
it. Remember this from RFC 974:
Note that the algorithm to delete irrelevant RRs breaks if LOCAL has
a alias and the alias is listed in the MX records for REMOTE. (E.g.
REMOTE has an MX of ALIAS, where ALIAS has a CNAME of LOCAL). This
can be avoided if aliases are never used in the data section of MX
RRs.
Besides that there are lots of instances where code would have to be
updated (I've got at least two instances myself!). Not everything does
lookups in such a way that further CNAMEs will be resolved!
Why do you want to make things more complex anyway? Why not K.I.S.S.
and just leave MX RRs as simple pointers to hostnames, the way they were
designed to be?
-- Greg A. Woods +1 416 218-0098 VE3TCP <> <> Planix, Inc. <>; Secrets of the Weird <> - To unsubscribe, send mail to with content (not subject): unsubscribe postfix-users
|
|
|