From owner-freebsd-questions@FreeBSD.ORG Mon Oct 26 23:13:48 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6B904106568B for ; Mon, 26 Oct 2009 23:13:48 +0000 (UTC) (envelope-from rstill74@gmail.com) Received: from mail-px0-f186.google.com (mail-px0-f186.google.com [209.85.216.186]) by mx1.freebsd.org (Postfix) with ESMTP id 3C4B88FC0A for ; Mon, 26 Oct 2009 23:13:48 +0000 (UTC) Received: by pxi16 with SMTP id 16so2224419pxi.3 for ; Mon, 26 Oct 2009 16:13:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=hV/yIWVsCHT1isAsXfv2ZvB+/zfxPDfcvi8QZAAsw7g=; b=kJPjdZAXgpJ3mdAF0qR9rP6UuQ5295qHzXioQGrX1Q7E/lLnaLaheIxNhj3U8tJrhl ALqdDpvrZ4FTqYKZWGFAwuuQ1GGvClyV2M1iQ8tRo8XLX+EbQlgOwtLxjS/N65+LZBFX 9s5r73uF5VQdAXnU4/Oz4aywIHKX17xf/L/GA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=PhorWuyB0Uk3rl6FrLK48UJIQD5KVKs48lo2JdiiimReN0L22y55f+NLTqL0eY+d/+ KS9tlUfSovNFDUujtzTsgl8ob7txBY+Uqf9yTd/MyTEt0RyEYiI2WO5CrbfGj/JDMAJM rJQyfhIGn2IpddFfu3ol6baMMDNtRlT9HPS2k= MIME-Version: 1.0 Received: by 10.142.2.14 with SMTP id 14mr667759wfb.15.1256598827739; Mon, 26 Oct 2009 16:13:47 -0700 (PDT) In-Reply-To: <22794_1256588088_4AE60338_22794_16_1_70C0964126D66F458E688618E1CD008A08CCEE85@WADPEXV0.waddell.com> References: <19358_1256579715_4AE5E283_19358_105_1_70C0964126D66F458E688618E1CD008A08CCEE70@WADPEXV0.waddell.com> <5e09dc040910261155t641ae7bbu79bc08d735d69db6@mail.gmail.com> <21272_1256584114_4AE5F345_21272_1_1_70C0964126D66F458E688618E1CD008A08CCEE7C@WADPEXV0.waddell.com> <22794_1256588088_4AE60338_22794_16_1_70C0964126D66F458E688618E1CD008A08CCEE85@WADPEXV0.waddell.com> Date: Mon, 26 Oct 2009 17:13:47 -0600 Message-ID: <5e09dc040910261613x4d91116epf397bfc35955f65d@mail.gmail.com> From: Ray Still To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: bind configuration issues X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Oct 2009 23:13:48 -0000 Ok, tell me just how nuts this idea is. To recap, two pipes, one destination. I set up second DNS server. ns1.example.com at 70.65..... (provider 1) ns2.example.com at 206.75....(provider 2) A records for example.org on ns1 will give 70.65..... on ns2 206.75.... if provider one goes down, ns1 is gone, ns2 is still available, and so is the route to the sites. It's not the best solution, but it's better than what I have. Am I missing something that's going to come back and bite me in the butt? Thanks, Ray On Mon, Oct 26, 2009 at 2:14 PM, Gary Gatten wrote: > I googled "dns round robin failover" and there are many hits. =A0One inte= resting one is: > http://forums.devshed.com/dns-36/ha-using-round-robin----working-368800.h= tml > > It suggests well written apps / resolvers will try to use all ip's return= ed by the query starting with the preferred one, not JUST the preferred one= . =A0Which means, just by enabling round robin with multiple A records, you= MAY get some level of HA/Failover by default. =A0Cool, BUT, I wouldn't bet= my life on it. =A0I'd still have something that could tweak your DNS recor= ds based on packet loss, latency, etc. =A0What if your circuit is "up", but= is degraded by loss, latency (load induced or otherwise), etc. > > As you mentioned, something is better than nothing - so start simple and = go from there! > > HTH! > > G > > > -----Original Message----- > From: owner-freebsd-questions@freebsd.org [mailto:owner-freebsd-questions= @freebsd.org] On Behalf Of Gary Gatten > Sent: Monday, October 26, 2009 2:07 PM > To: Ray Still; freebsd-questions@freebsd.org > Subject: RE: bind configuration issues > > I'm not intimate with bind, or anything/one actually - but that's another= story... > > Anyway, the gist is you need to "ping" some public hosts from your dns se= rver (or another system I guess, but easier if on the dns server). =A0One d= estination host would be reachable through one connection, and the other of= course would only be reachable through the alternate connection. =A0Maybe = use the primary DNS servers each upstream ISP provides to you? =A0Anyway, i= f both pings are OK, then your DNS server does round-robin for the host(s) = in question. =A0If one ping fails, then you stop handing out that IP. =A0Yo= u can for the route taken within ping itself, or use static host(/32) route= s, etc. > > Sounds simple huh? =A0It kinda is, and LONG ago I had a shell script to d= o just this, but it's gone - and maybe bind 9+ has some sort of this functi= onality available to you embedded in the bind code? =A0Don't know. =A0Even = if you have to write your own script to update your dns records based on yo= ur monitoring process it's not that hard even for a scripting novice such a= s myself! > > G > > > -----Original Message----- > From: owner-freebsd-questions@freebsd.org [mailto:owner-freebsd-questions= @freebsd.org] On Behalf Of Ray Still > Sent: Monday, October 26, 2009 1:56 PM > To: freebsd-questions@freebsd.org > Subject: Re: bind configuration issues > > On Mon, Oct 26, 2009 at 11:55 AM, Gary Gatten wrote= : >> >> You certainly don't "need" BGP for this, the DNS thing will work, but wi= ll be a bit kludgy and certainly not as ... "responsive" to failures - a la= query caching, TTL's and what not. >> >> ----- Original Message ----- >> From: owner-freebsd-questions@freebsd.org >> To: Ray Still >> Cc: freebsd-questions@freebsd.org >> Sent: Mon Oct 26 12:50:56 2009 >> Subject: Re: bind configuration issues >> >> On Oct 26, 2009, at 10:03 AM, Ray Still wrote: >> > Hello, >> > I am adding a redundant Internet connection to my current hosting >> > setup and >> > I need to figure out how to set up the DNS to make this work. >> >> The two issues normally aren't related. >> >> If both connections are from the same provider, talk to them about >> multilink PPP; if they are from different providers, you need to look >> into multihoming and getting your own AS #. >> > > two different providers. > >> >> > Current setup: >> > freebsd 7.0 machine, one local IP address, runs web, mail, and name >> > server. >> > static ip address in router. >> > I have two DNS servers registered, but they both point to the same ip >> > address an the same machine. (Yes, I should have my fingers slapped.) >> > >> > Desired setup >> > same machine, one local IP address, runs web, mail, and name server. >> > different router (Linksys RV082) with 2 static ip address. >> >> In order to have redundancy, you need to have two real, separate >> machines, each of which is running BIND, each of which is on a >> separate routable IP.=A0 This is an orthogonal issue to setting up >> multiple Internet connections. > > Yes, In an ideal world I would do this. The two machines would also be > in separate buildings/cities/provinces/countries/planets > (pick your level of paranoia)=A0 ;) > However, reducing single points of failure is an improvement, even if > I can't eliminate them. > > >> >> > How do I set up bind so that >> > 1) bandwidth is shared between the two connections, >> > and >> > 2) if one goes down, the other keeps working. >> > I had a few ideas, but they all seem to have flaws. >> >> You can't set up BIND to control multilink aggregation and failover; >> that's not what it does. >> >> Regards, >> -- freebsd-questions@freebsd.org >> -Chuck >> > > Thanks for the replies. > Chuck, thanks for the keywords to search. Some of what I'm finding > looks like a solution for companies a lot bigger than me, but I'll > keep looking. > > Gary, can you give me any clues about how to do it with just DNS? Yes, > I do realize that this leaves single points of failure, but at least > they would be points that I could do something about if necessary. > > Thanks again, > Ray >> >> _______________________________________________ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.= org" >> >> "This email is intended to be reviewed by only the intended recipient an= d may contain information that is privileged and/or confidential. If you ar= e not the intended recipient, you are hereby notified that any review, use,= dissemination, disclosure or copying of this email and its attachments, if= any, is strictly prohibited. If you have received this email in error, ple= ase immediately notify the sender by return email and delete this email fro= m your system." > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.o= rg" > > > > > > >
>
> "This email is intended to be reviewed by only the intended recipient > =A0and may contain information that is privileged and/or confidential. > =A0If you are not the intended recipient, you are hereby notified that > =A0any review, use, dissemination, disclosure or copying of this email > =A0and its attachments, if any, is strictly prohibited. =A0If you have > =A0received this email in error, please immediately notify the sender by > =A0return email and delete this email from your system." > > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.o= rg" > > > > > > >
>
> "This email is intended to be reviewed by only the intended recipient > =A0and may contain information that is privileged and/or confidential. > =A0If you are not the intended recipient, you are hereby notified that > =A0any review, use, dissemination, disclosure or copying of this email > =A0and its attachments, if any, is strictly prohibited. =A0If you have > =A0received this email in error, please immediately notify the sender by > =A0return email and delete this email from your system." > > >