From owner-freebsd-questions@FreeBSD.ORG Wed Dec 28 16:41:05 2011 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 191C11065672 for ; Wed, 28 Dec 2011 16:41:05 +0000 (UTC) (envelope-from andreev.peter@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id A4FF78FC13 for ; Wed, 28 Dec 2011 16:41:04 +0000 (UTC) Received: by wgbdr11 with SMTP id dr11so22260013wgb.31 for ; Wed, 28 Dec 2011 08:41:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=xLmOF8OGEdptv8kZavatkDGzgxKkuKpM1ic9xIefRsE=; b=KJLV4Xs7to+aoExY54ffXz9ly39/uWvNfm0i0YHe8oeDAcjwNoYJ9k10yDfJ6a3cIT ASy+9C8y8ffGprUKfgu6IpuFUudg5qT1imhu0owtQthSRACK8RcvTcdaTBh0QFlu2PNP MaC3KD4QzXXP6yvB66/d6YZM5cHGdYwopvtpM= MIME-Version: 1.0 Received: by 10.227.207.82 with SMTP id fx18mr32246182wbb.19.1325088753171; Wed, 28 Dec 2011 08:12:33 -0800 (PST) Received: by 10.216.15.77 with HTTP; Wed, 28 Dec 2011 08:12:33 -0800 (PST) In-Reply-To: References: <20111228075422.GA18064@admin.sibptus.tomsk.ru> <4EFAE80D.9040900@my.gd> <20111228130734.GA23763@admin.sibptus.tomsk.ru> <4EFB1B4F.2090504@my.gd> Date: Wed, 28 Dec 2011 19:12:33 +0300 Message-ID: From: Peter Andreev To: freebsd Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: mutual forwarders in ISC BIND 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: Wed, 28 Dec 2011 16:41:05 -0000 2011/12/28 Damien Fleuriot : > > > On 12/28/11 2:07 PM, Victor Sudakov wrote: >> Damien Fleuriot wrote: >>> >>> If you're trying to build up a cache to improve performance and respons= e >>> time, here's your scenario: >>> >>> DNS C, forward to DNS A,B for all queries >>> DNS D, forward to DNS B,A for all queries >>> >>> Your cache will start building up and only responses that are not cache= d >>> will be taken from your NS A and B servers. >> >> Sorry, I fail to see how this is any better than two independent DNS >> servers. Perhaps a variant like >> >> DNS C, forward to DNS A >> DNS D, forward to DNS A >> >> would be close to the goal of cache consolidation. >> > > DNS A suffers an outage ; you're fucked, to put it bluntly. BIND can be configured to deal with such troubles. =A0But still Victor's idea isn't very good. First of all because response time increasing in case of using forwarders. Victor, we researched this topic and learned that response time highly depends on distance between user and resolver, while cache influence on this value is lesser. So I advice you to keep all as is. > > >> Matthew Seaman wrote: >>> >>> If you want to consolidate caches then probably your best bet is to hav= e >>> fewer, but larger resolvers. =A0A pretty standard server class machine >>> dedicated to recursive DNS should be easily capable of supporting many >>> thousands of clients. >> >> You are certainly right. >> >>> >>> DNS is not really a fruitful target for reducing traffic volume -- ther= e >>> really isn't that much of it compared to all other types in any case. >>> It's also pretty critical to the perceived performance of your networks= . >>> =A0Complicating and slowing down the DNS lookup path just makes everyth= ing >>> look slow. >> >> I just wanted the servers to benefit from each other's caches. That >> could speed up the lookups. >> >> > > On a side note, have you considered unbound ? > > It may be better suited to your needs and scale. > _______________________________________________ > 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" -- -- AP --=20 -- AP