From owner-freebsd-isp Mon Apr 17 12: 6:28 2000 Delivered-To: freebsd-isp@freebsd.org Received: from federation.addy.com (federation.addy.com [208.11.142.20]) by hub.freebsd.org (Postfix) with ESMTP id 208B437B939 for ; Mon, 17 Apr 2000 12:06:25 -0700 (PDT) (envelope-from jim@federation.addy.com) Received: from localhost (jim@localhost) by federation.addy.com (8.9.3/8.9.3) with ESMTP id PAA25999; Mon, 17 Apr 2000 15:06:07 -0400 (EDT) (envelope-from jim@federation.addy.com) Date: Mon, 17 Apr 2000 15:06:07 -0400 (EDT) From: Jim Sander To: bv@wjv.com Cc: freebsd-isp@FreeBSD.ORG Subject: Re: Failover question/idea/hint In-Reply-To: <200004171625.MAA39745@mail.wanlogistics.net> 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 > if the primary DNS (located at tha main site) goes down, would that be > enough to force it to the secondary name server - which I'm thinking > could point to the backup site. One possible problem is that certain internet hosts set up their nameservers to querry the secondary server before the primary... at least one ISP I know of does/did that. Why- I suppose they think it's faster? (and maybe it is...) Don't know how common it is, but it *does* happen. It's not so much a problem as something to keep in mind. In other words, don't set up their DNS box to serve out IP of the "backup" site "ahead of time" unless they want synchronization issues and the like. It's a good strategy, but i don't think it can't be as automatic as one might like- unless you layer something over it, or do something else. -=Jim=- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message