At 18:40 07-03-00 , John.ksi(at)webplus.net wrote:
>> [I would emphatically _not_ recommend using multiple A records
>> to do what a CNAME is intended (and appropriate) to do.]
>
>Permit me to pick up on this and pick your brain more....?

See in particular the discussion in STD 13 (RFC 1034) at "3.6.2. Aliases
and canonical names."

Recommended practice, as I understand it, is to define the main DNS name
with an A record and with reverse DNS lookup properly configured. Then
additional names are defined via a CNAME resource record (RR).

This allows reverse DNS lookup verification to work... a given name either
matches the host name or to the host name of which the given name is a
CNAME alias.

By contrast, with multiple A resource records, a reverse DNS lookup
verification will (hopefully) match for one of them... but fail for the
others.

This also has the other benefits mentioned in STD 13 at 3.6.2. Aliases and
canonical names.

Nor can I imagine that you can find a benchmark anywhere that can actually
measure a performance benefit, much less one that matters.

Safe computing,  /Harold
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Harold A. Driscoll                 mailto:Harold(at)Driscoll.Chi.IL.US
#include <std/disclaimer>                 http://Driscoll.Chi.IL.US

• Web Designer Courses
• Off the Shelf Training Courses

HWG: hwg-servers mailing list archives, maintained by Webmasters @ IWA