From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1RSjey-0001ka-OH for garchives@archives.gentoo.org; Tue, 22 Nov 2011 06:16:49 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 3C1A321C1B6; Tue, 22 Nov 2011 06:16:21 +0000 (UTC) Received: from der-root.de (der-root.de [78.46.36.110]) by pigeon.gentoo.org (Postfix) with ESMTP id AF46421C055 for ; Tue, 22 Nov 2011 06:15:33 +0000 (UTC) Received: from [10.0.2.15] (der-root [78.46.36.110]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by der-root.de (Postfix) with ESMTPSA id D5513220C2D0 for ; Tue, 22 Nov 2011 07:15:31 +0100 (CET) Message-ID: <4ECB3E01.7030406@smash-net.org> Date: Tue, 22 Nov 2011 07:15:29 +0100 From: =?UTF-8?B?Tm9ybWFuIFJpZcOf?= User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.2.20) Gecko/20110804 Lightning/1.0b2 Thunderbird/3.1.12 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-server@lists.gentoo.org Reply-to: gentoo-server@lists.gentoo.org MIME-Version: 1.0 To: gentoo-server@lists.gentoo.org Subject: Re: [gentoo-server] Failover-capable DNS server? References: In-Reply-To: X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Archives-Salt: c420a8a8-e5b1-4b21-be08-b29d89fea98f X-Archives-Hash: f3d3c1e0cfc7e0feb5bfb86de01cf60c -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/21/11 10:52, Pandu Poluan wrote: > Hello all, I'm in need of some suggestions. > > You see, I have 2 Internet connections with public IP addresses, let's > say ISP A 11.22.33.44 and ISP B 22.33.44.66 > > Now, I want outside parties trying to connect to "target.example.com" > by default resolves to 11.22.33.44, but if ISP A's connection goes > down for any reason, the DNS server will instead return "22.33.44.66". > > The nameserver itself will be located in the company, accessible from > the world via "ns1.example.com" = 11.22.33.44:53 or "ns2.example.com" > = 22.33.44.66:53. This allows the nameserver to monitor the state of > the connections to ISP A and ISP B. > > I've been perusing pages discussing BIND, and came to the conclusion > that BIND is incapable of doing that. > > Anyone can recommend me a DNS server that has such capability? Or how > to implement this ability with maybe Python or (*shivers*) Perl? > > Rgds, Hello, you could use another way, by switching the IP address of the DNS server with Heartbeat acordingly. Say you have a server with IP A and another with IP B. You can tell heartbeat to switch an IP C as second IP between these servers. So if Server 1 ist master, it has IP A and C. If it goes down, Server 2 will bring IP C up and become master. IP C will be you ns dns record obviously. You can avoid splitbrains when a network component between these machines goes down by wiering them crossover on a second NIC. Even saver would be a STONITH device, which kills the whole machine if one of the servers is reachable and answers to ping but is doing crap. A client side way would be a resolve.conf looking like this: nameserver 11.22.33.44 nameserver 22.33.44.66 options timeout:1 search your.domain regards, Norman -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJOyz4BAAoJEMCA6frkLT6zcGMH/RhfutaeDKtelQsRotGDfEjb z9dWgWJs+YBC4P16AGw9ZGEQ8b1zOjhnj4mjjkCPQohik0A4tCLHqUX0tC2QeJSN 4fErfaqInOqqPHmcvEOYBREG09dC0VoqGC9MjzvOKn2yYUbaBdt8Foc8o6DHICKi rZMl2KGWIUUSv4/uhbaqpd3mEceqGB33XjssvYDis1douPz4TgZTexYlC/gX+OtF l8eUDdEWy6ks+BM712CLqWAp45zgv3QPQvNQiPyOUU++LQ7vW5FLmlz6fHl9xUtw SjqUC+9Ry17VdSTBSMtmiTZjaXoR2LFZPiVvFnIKYKvJE/Fa3sDMtLFQTF1u0SE= =dKBC -----END PGP SIGNATURE-----