From owner-freebsd-current Fri Jan 21 14:53:24 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 B12B6155D1 for ; Fri, 21 Jan 2000 14:53:11 -0800 (PST) (envelope-from oppermann@pipeline.ch) Received: (qmail 2971 invoked from network); 21 Jan 2000 22:51:06 -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 22:51:06 -0000 Message-ID: <3888E32A.522E1FE7@pipeline.ch> Date: Fri, 21 Jan 2000 23:52:26 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.03 [en] (WinNT; U) MIME-Version: 1.0 To: Brad Knowles 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> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brad Knowles wrote: > > At 11:06 PM +0100 2000/1/21, Andre Oppermann wrote: > > > Thats not so easy. What about this: > > > > cvsup IN CNAME cvsup1.freebsd.org. > > cvsup IN CNAME cvsup2.freebsd.org. > > cvsup IN CNAME cvsup3.freebsd.org. > > cvsup IN CNAME cvsup4.freebsd.org. > > cvsup IN CNAME cvsup5.freebsd.org. > > cvsup IN CNAME cvsup6.freebsd.org. > > cvsup IN CNAME cvsup7.freebsd.org. > > cvsup IN CNAME cvsup8.freebsd.org. > > As I understood the rules of good Domain Administration, > everything that is publicly visible in your network needs to have an > MX record. But with this scheme you can't give cvsup.freebsd.org an > MX record, because pointing an MX at a CNAME violates the RFC. You can, simply do this: cvsup IN MX 10 hub.freebsd.org No violation of any RFC whatsoever. > Personally, I would much prefer the CPAN solution of a program > that takes the IP address of the query source, and then using > knowledge of what IP addresses are generally located where in the > world (available via the whois maps in the various regions, which > could presumably be imported and stored locally), returns a short > list of addresses in the preferred order. For those networks where > multiple addresses may have equal "cost", it can then randomize for > load balancing purposes. Don't go by whois, it does not reflect the physical connectivity. Go by BGP path length if you want to do something like this. > It requires either a hacked nameserver program for this one zone, > or the code to handle this has to be incorporated into cvsup itself, > so that you distribute the logic and CPU processing time to all the > clients. There are commecial nameservers which decide upon bgp path length but it'll cost some big $$$. -- Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message