On Thu, 3 May 2001, Kris von Mach wrote:
> Why can't it be a CNAME? Is there a reason for this? I am currently using it
> as a CNAME and it's been working fine for a year or so... If there is a good
> reason for it, I sure would like to know so I can make changes.
The CNAME RR means "this machine's function has now been replaced by this
other machine", which is fine if you want to allow people to keep using
the old name for a service, but you should update your MX records to point
to its new one.
Also chasing down CNAMEs increases the work that has to be done for each
message.
And, which qmail usually manages to handle them sensibly, they can cause
it problems when it's talking to other popular MTAs that think CNAME
records are illegal in all header lines
> Oh I have this currently:
<snip>
> Or did you mean that you can't have something like this:
>
> IN MX 10 mail
> IN A 63.165.246.3
> www IN A 63.165.246.3
> mail IN CNAME swishmail.com.
Doesn't that achieve the same effect as your previous example? bind
really should reject this unless you've set an option to let it pass with
just a warning. You should have this instead:
$origin swishmail.com.
IN MX 10 mail
IN A 63.165.246.3
www IN A 63.165.246.3
mail IN A 63.165.246.3
(you should also consider djbdns for your own servers, which makes it
harder to make mistakes like that in the first place. But that's best
argued elsewhere)
--Colin
Colin Palmer -- [EMAIL PROTECTED] -- http://raccoon.osoal.org.nz/
Systems Engineer -- [One Short Of A Llama] http://web.osoal.org.nz/
