Received: from localhost (daemon@localhost) 
        by CS.UTK.EDU with SMTP (cf v2.9s-UTK)
	id XAA20092; Mon, 7 Oct 1996 23:53:02 -0400
Received: by CS.UTK.EDU (bulk_mailer v1.7); Mon, 7 Oct 1996 23:51:39 -0400
Received: from CU.NIH.GOV (cu.nih.gov [128.231.64.111]) 
        by CS.UTK.EDU with SMTP (cf v2.9s-UTK)
	id XAA20005; Mon, 7 Oct 1996 23:51:36 -0400
Message-Id: <199610080351.XAA20005@CS.UTK.EDU>
To: hostmaster@munnari.oz.au, ERIC@VM.SE.LSOFT.COM
cc: moore@cs.utk.edu, drums@cs.utk.edu
From: "Roger Fajman" <RAF@CU.NIH.GOV>
Date:     Mon, 07 Oct 1996  23:52:33 EDT
Subject:  Re:  cname lookup effort

> Agreed, multiple IP's are a horrible solution.
>
>     when all that is  needed is a  CNAME that
>     doesn't rewrite 822 headers (I said 822, not 821).
>
> ie: an MX.   And just maybe the new SRV record for other services
> (though I'm not sure I know of any that care about what name was
> used).
>
> kre

One common reason is a service provider running one WWW server to
serve multiple customers.  When a user connects to www.abc.com,
he should see the ABC Corp. home page.  When someone connects to
www.xyz.com, she should see the XYZ Corp. home page.