Christian Seberino wrote:
The super-genius security guy that wrote qmail also wrote
a paper on why CNAME is a bad idea.......
So should everyone NEVER use it?
Can you ALWAYS get the same result by just using more
A records???
e.g. Use 2 A records to set www.mydomain.com and mydomain.com
to SAME IP address without CNAMEs!!!
chris
------------------------------------------------------------------------
I've read the arguments, and agree with his rationals for not using
CNAME, but I don't believe that his rational is reason enough to
completely avoid using them. The biggest problem is it can get messy if
CNAME are pointing to CNAME pointing CNAME, and so on.
CNAME is useful for a lot of things in a world with dynamic IP
addresses. I use CNAME for pointing to hosts in other domains that may
change IPs. Something like jason.bar.com =>
jason.customer.bar.foo.com. I don't control anything but my content at
the latter, so IP and such may change without my knowing. This allows me
to give a short name for it.
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
