|
North American Network Operators Group Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical RE: LoadBalancing products: Foundry ServerIron
>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:[email protected]] 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.
|