From owner-freebsd-isp Wed Aug 11 8:33:33 1999 Delivered-To: freebsd-isp@freebsd.org Received: from proteus.eclipse.net.uk (proteus.eclipse.net.uk [195.188.32.118]) by hub.freebsd.org (Postfix) with ESMTP id 64C5A1553D for ; Wed, 11 Aug 1999 08:33:29 -0700 (PDT) (envelope-from stuart@eclipse.net.uk) Received: from eclipse.net.uk (elara.eclipse.net.uk [195.188.32.31]) by proteus.eclipse.net.uk (Postfix) with ESMTP id 90FA59B20; Wed, 11 Aug 1999 16:31:24 +0100 (BST) Message-ID: <37B197BF.97C095B0@eclipse.net.uk> Date: Wed, 11 Aug 1999 16:33:19 +0100 From: Stuart Henderson Organization: Eclipse Networking Ltd. X-Mailer: Mozilla 4.61 [en] (WinNT; I) X-Accept-Language: en-GB MIME-Version: 1.0 To: Chris Shenton Cc: Barrett Richardson , Steve Hovey , Mitch Vincent , freebsd-isp@FreeBSD.ORG Subject: Re: Loadbalance webservers References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > So the multiple records are a bit of a hack Yep, > and will hose you if one of the servers dies. Not really - most web browsers, proxies and telnets cycle through until they find one that answers. Round robin DNS is in common enough usage that it is quite well supported by client software. (Also, bind will randomise the order and puts local networks first). > It would be way cool to modify the server-based daemon to have it > determine the network distance/cost to the *client* then feed that to > the lbnamed so it could return a record corresponding to the server > fastest/closest to the actual client. This would implement WAN load > balancing much like F5 Lab's $27K (each) 3DNS. I think Netscape used to do this in software (at least I always used to get the IP address of their UK mirror returned) but they seem not to be doing that now. Stuart To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message