[29724] in North American Network Operators' Group
RE: LoadBalancing products: Foundry ServerIron
daemon@ATHENA.MIT.EDU (Karyn Ulriksen)
Thu Jul 6 14:10:01 2000
Message-ID: <0127E258EE29D3118A0F00609765B448317876@subnet-gw-00053.sitestream.net>
From: Karyn Ulriksen <kulriksen@publichost.com>
To: "'Peter C. Norton'" <spacey@lenin.nu>
Cc: "'nanog@merit.edu'" <nanog@merit.edu>
Date: Thu, 6 Jul 2000 11:07:57 -0700
MIME-Version: 1.0
Content-Type: text/plain;
charset="windows-1252"
Errors-To: owner-nanog-outgoing@merit.edu
>The delegation isn't that big an issue. If you want, you can attach
>multiple A records to your SOA, and have all of the servers answering the
>domain.com return a redirect for the client to www.domain.com.
I hope you aren't talking about cnaming domain.com to www.domain.com [hair
raising on end]... of course, you arent. And you aren't talking about
taking a farm of about 12,000+ sites and setting up rewrite rules... And
you arent talking about coordinating 12,000+ sites A records across two DNS
systems....
OK, I'm all ears...
-----Original Message-----
From: Peter C. Norton [mailto:spacey@lenin.nu]
Sent: Thursday, July 06, 2000 10:56 AM
To: Karyn Ulriksen
Subject: Re: LoadBalancing products: Foundry ServerIron
On Thu, Jul 06, 2000 at 09:48:17AM -0700, Karyn Ulriksen wrote:
>
> >Right. However the common solution is to delegate a small subdomain just
> >for the 3dns'ed RR's to it (and perhaps cname to them from the top
level).
>
> I figured. And also considered the sub-delegation. Only one problem.
More
> often than not the website "www.domain.com" also wants "domain.com"
pointing
> to their service. If you point it all at the 3DNS, that kind of blows the
> sub-delegation theory. AND, if you sub-delegate the "www.domain.com" and
> put an entry in the domain.com zone record on your regular DNS server - it
> can be managed OK for a few domains, but what about when you have a very
> large server farm... [eyes rolling] gads!
The delegation isn't that big an issue. If you want, you can attach
multiple A records to your SOA, and have all of the servers answering the
domain.com return a redirect for the client to www.domain.com.
--
The 5 year plan:
In five years we'll make up another plan.
Or just re-use this one.
