CName Terminology Question

[Johnny Fribert Lauridsen]

Luckily,
many providers and companies deploys some load balancing/redundancy devices in front of their server farms, so that
they can change addresses, add new servers, remove servers, etc., on flight, without having to
care about DNS.  One DNS entry for all (identical) servers, no matter what their 'real' ip address or domainname is like.
The DNS entry points to a virtual IP addr on the load balancing device.  This device then keeps a track
of the real servers (load, out-of-service, in-service, etc.).
Johnny

At 14:58 14/04/2000 +0000, Barry Margolin wrote:
>In article <38F677E8.38EF9EC6 at tmca.com.au>,
>Stanley Liu  <stanley.liu at tmca.com.au> wrote:
> >After reading Barry' reply (thanks Barry), I was still not quite convinced why we
> >have the CNAME construct - if we can do the same using A records, why
> >bother to have
> >CNAMEs since they have so many restrictions.  
>
>This allows you to alias www.yourdomain.com to www.yourhostingcompany.net.
>If the hosting company changes the address of their server, you don't have
>to update your domain.
>
>Without CNAMEs, they would have to get *all* of their customers to update
>their domains when they change the address of the server.
>
>-- 
>Barry Margolin, barmar at genuity.net
>Genuity, Burlington, MA
>*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
>Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.