From owner-freebsd-current Fri Jan 21 15:14: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by hub.freebsd.org (Postfix) with SMTP id DA6C61561E for ; Fri, 21 Jan 2000 15:13:53 -0800 (PST) (envelope-from oppermann@pipeline.ch) Received: (qmail 3300 invoked from network); 21 Jan 2000 23:11:48 -0000 Received: from unknown (HELO pipeline.ch) ([195.134.128.41]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 21 Jan 2000 23:11:48 -0000 Message-ID: <3888E804.1BA82919@pipeline.ch> Date: Sat, 22 Jan 2000 00:13:08 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.03 [en] (WinNT; U) MIME-Version: 1.0 To: "Louis A. Mamakos" Cc: Garance A Drosihn , John Polstra , current@FreeBSD.ORG Subject: Re: Please help spread the CVSup mirror load more evenly References: <3888D870.2416BFE8@pipeline.ch> <200001212214.RAA02259@whizzo.transsys.com> <3888E18E.F1CBA39B@pipeline.ch> <200001212259.RAA02836@whizzo.transsys.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Louis A. Mamakos wrote: > > > > Second, a domain name can at most a single CNAME record associated > > > with it, and other other record types. BIND will (should) barf on a > > > zone file containing the example you listed. > > > > It does not. It will round-robin over the CNAME's. > > If it does, than this is a bug in BIND. The DNS is not defined to > work this way. Semantically, it doesn't make sense to have more > than one CNAME record. The CNAME resource record is supposed to > contain the cannonical name for the domain name that it's associated > with. There can be only one cannonical name. > > And it appears that in the latest BIND, they've seen the error of their > ways: -snip- OK, I did it with bind 8.1.2, see my other response to Steinar. > In any case, this has turned into a debate on how to (ab)use BIND and > the DNS, and is well off topic. Back on topic. Do it instead with A records. Joe Random goes for cvsup.freebsd.org and highly likely wont be cvsupping more than once a day. Others who do can hardwire to one specific cvsup server. The best of both worlds with just a few key strokes and now complies with every imaginable RFC. Uh, I better don't pray for it. > > Yea, then all swamp cvsup8.freebsd.org and John has to send another > > message that there are still cvsup[2-7].freebsd.org idling around. > > Just kidding... But you get the point? > > My only point is that the first response to a problem isn't to necessarily > pull out emacs and start hacking away on code. Yea, it is easier to do in a regular zone file then to implement the network measurement logic into cvsup. -- Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message