From owner-freebsd-isp Mon Jan 15 2: 7:17 2001 Delivered-To: freebsd-isp@freebsd.org Received: from sai.co.za (mail.sai.co.za [196.33.40.37]) by hub.freebsd.org (Postfix) with ESMTP id CF63237B401 for ; Mon, 15 Jan 2001 02:06:54 -0800 (PST) Received: from fdisk ([196.33.40.17]) by mail.sai.co.za (SBMail MTA v2.11(1096) SMTPD32) with ESMTP id AA9376; for ; Mon, 15 Jan 2001 12:05:59 0200 (South Africa Standard Time) From: "Dave Wilson" To: "Matthew Horoschun" Cc: Subject: RE: DNS redundancy & load balancing Date: Mon, 15 Jan 2001 12:07:33 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-reply-to: <3A63C980.92F7022@actweb.net> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Importance: Normal Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Matthew, Indeed but clients have their primary DNS server set to our primary, thus if our primary goes down no resolution takes place. Clients have a their seconday DNS set to our secondary DNS, but we've found that often M$ machines never even try looking at their secondary DNS server. Any ideas ? Kindest regards David Wilson The S.A Internet #include -----Original Message----- From: Matthew Horoschun [mailto:matthew@actweb.net] Sent: 16 January 2001 06:10 To: Dave Wilson Cc: Wayne@Sai.Co.Za Subject: Re: DNS redundancy & load balancing Dave, DNS is an internally redundant protocol. That is, there is no need to do anything fancy - all you need to do is make sure your other nameserver is acting as a secondary for all the zones on your primary nameserver. Of course, you should really have a secondary nameserver which isn't attached to your local network - to protect against situations when you loose connectivity. Matthew. Dave Wilson wrote: > Hi guys, howzit going ? > > 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. > > I know little about load balancing or clustering so any input would be > appreciated. > Thanks. > > Kindest regards > David Wilson > The S.A Internet > > #include > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isp" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message