From owner-freebsd-isp Mon Jan 15 7:58:23 2001 Delivered-To: freebsd-isp@freebsd.org Received: from heaven.gigo.com (heaven.gigo.com [209.0.55.69]) by hub.freebsd.org (Postfix) with ESMTP id 4297837B400 for ; Mon, 15 Jan 2001 07:58:07 -0800 (PST) Received: from localhost (localhost.gigo.com [127.0.0.1]) by heaven.gigo.com (Postfix) with ESMTP id 501761705E; Mon, 15 Jan 2001 07:58:01 -0800 (PST) Date: Mon, 15 Jan 2001 07:58:01 -0800 (PST) From: Jason Fesler To: Dave Wilson Cc: Matthew Horoschun , Subject: RE: DNS redundancy & load balancing In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > 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 ? Move your DNS servers to different IP addresses, ones that are not published. Assign virtual IP addresses (the published ones). If you have a DNS failure or host failure, you can remove (if needed) the published virtual IP, and put it on as a second virtual IP on the remaining host. If you're good, you can even automate this with creative use of a third host for monitoring and administering the IP changes. OF course, you can also just solve this with hardware, ala Alteons and their like, but most ISP's are too cheap. [Been there, done that, got screwed on the tshirt. ;-)] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message