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 1RSQiq-00025I-LC for garchives@archives.gentoo.org; Mon, 21 Nov 2011 10:03:33 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 1E421E04E7; Mon, 21 Nov 2011 10:03:12 +0000 (UTC) Received: from mail-gx0-f181.google.com (mail-gx0-f181.google.com [209.85.161.181]) by pigeon.gentoo.org (Postfix) with ESMTP id 1FCD121C024 for ; Mon, 21 Nov 2011 10:02:36 +0000 (UTC) Received: by ggnv2 with SMTP id v2so5670655ggn.40 for ; Mon, 21 Nov 2011 02:02:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hyves.nl; s=hyves-g; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=PTh/EGSPQY5AbKkL250iZQwears70Y0HasS3fX6eas4=; b=UH3ngKyHnI1RcPZbDNEIUxUXSrS+auuijIlboH26+vikGmIQtmjYul/reNy4GP4diB j/eVf+mOTW+BUniqFN2RFd58/nGEeeGH06vaZJ7I0XON3QEB2UE6z708S0Rep1UvYz2n XeTOdUjPugr2LkhfoaZzLRyE3uxFsV8lt6u4g= 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 Received: by 10.101.210.13 with SMTP id m13mr2790505anq.168.1321869756237; Mon, 21 Nov 2011 02:02:36 -0800 (PST) Received: by 10.236.153.129 with HTTP; Mon, 21 Nov 2011 02:02:36 -0800 (PST) In-Reply-To: References: Date: Mon, 21 Nov 2011 11:02:36 +0100 Message-ID: Subject: Re: [gentoo-server] Failover-capable DNS server? From: Jos Houtman To: gentoo-server@lists.gentoo.org Content-Type: multipart/alternative; boundary=0016e68ee2d342880304b23bc931 X-Archives-Salt: 02eb27c2-45de-4494-b899-7b08fc793a96 X-Archives-Hash: 69433b7c61fbf77b6c3dc4bc1ecdfd04 --0016e68ee2d342880304b23bc931 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi, Why don't you create a short lived (say 5 minutes) A record for target.example.com. Under normal circumstances both ns1 and ns2 will return 11.22.33.44 You can then create a script that monitors the internet connection of isp A= . If that is down, it will update the A records for target.example.com to the secondary IP adress. Because your A record has a short timeout, downstream clients should pick up the new ip address relatively quickly. However you have to be aware that some ISP ignore such short lived A records and cache the resolved address for a longer period of time. Depending on your internet connection, I might consider offloading this burden to a hosting company. Jos On Mon, Nov 21, 2011 at 10:52 AM, 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" =3D 11.22.33.44:53 or "ns2.example.com" > =3D 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, > -- > FdS Pandu E Poluan > ~ IT Optimizer ~ > > =95 LOPSA Member #15248 > =95 Blog : http://pepoluan.tumblr.com > =95 Linked-In : http://id.linkedin.com/in/pepoluan > > --0016e68ee2d342880304b23bc931 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable
Hi,

Why don't you create a short lived (say 5 = minutes) A record for target.example.= com.
Under normal circumstances both ns1 and ns2 will return 11.22.= 33.44

You can then create a script that monitors the internet connection of i= sp A.
If that is down, it will update the A records for target.example.com to the secondary IP a= dress.

Because your A record has a short timeout, downstream c= lients should pick up the new ip address relatively quickly.
Howe= ver you have to be aware that some ISP ignore such short lived A records an= d cache the resolved address for a longer period of time.
=A0
Depending on your internet connection, I might consider = offloading this burden to a hosting company.=A0

Jos

On Mon, Nov 21, 2011 at 10:52 AM, Pandu Poluan <pandu@poluan.info>= wrote:
Hello all, I'm in need of some suggesti= ons.

You see, I have 2 Internet connections with public IP addresses, let's<= br> 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&q= uot;.

The nameserver itself will be located in the company, accessible from
the world via "ns= 1.example.com" =3D 11.22.33.44:53 or "ns2.example.com"
=3D 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,
--
FdS Pandu E Poluan
~ IT Optimizer ~

=A0=95 LOPSA Member #15248
=A0=95 Blog : http= ://pepoluan.tumblr.com
=A0=95 Linked-In : http://id.linkedin.com/in/pepoluan


--0016e68ee2d342880304b23bc931--