From owner-freebsd-isp Mon Jan 15 1: 1:14 2001 Delivered-To: freebsd-isp@freebsd.org Received: from mgw1.MEIway.com (mgw1.meiway.com [212.73.210.75]) by hub.freebsd.org (Postfix) with ESMTP id 4AA0337B401 for ; Mon, 15 Jan 2001 01:00:56 -0800 (PST) Received: from sv.Go2France.com (sv.meiway.com [212.73.210.79]) by mgw1.MEIway.com (Postfix Relay Hub) with ESMTP id EF0116A909 for ; Mon, 15 Jan 2001 10:00:54 +0100 (CET) Message-Id: <5.0.2.1.0.20010115095305.02352ec0@mail.Go2France.com> X-Sender: lconrad%Go2France.com@mail.Go2France.com X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Mon, 15 Jan 2001 09:59:10 +0100 To: freebsd-isp@freebsd.org From: Len Conrad Subject: Re: DNS redundancy & load balancing In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >We have a primary & secondary DNS server on our local network. >We need some utility or setup that will automatically allow our secondary >DNS to totally take over from our primary DNS in the event our primary DNS >goes down. > >This means effectively that that in the event of a primary DNS failure our >secondary DNS must be able to change it's own IP address to that of the dead >primary DNS server and take over all resolution etc. If both DNS's are in the delegation data for a zone, then the standard query behavior of resolvers and other DNS's will query all delegated DNS's until they get a response. To "DNS clients", there is not a primary or secondary DNS for a zone, all its NS records. Losing one of two NS's is not fatal, and will only slow 50% of the queries that will timeout before trying the other DNS. Load sharing among all DNS's for a zone is already acomplished by DNS altering the physical order of NS records for each query. Len http://BIND8NT.MEIway.com : Binary for ISC BIND 8.2.3 T9B for NT4 & W2K http://IMGate.MEIway.com : Build free, hi-perf, anti-spam mail gateways To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message