From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15670 invoked by uid 1002); 16 Oct 2003 07:19:17 -0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 6598 invoked from network); 16 Oct 2003 07:19:16 -0000 Date: Thu, 16 Oct 2003 10:17:30 +0300 (EEST) From: Andrei Ivanov X-X-Sender: shadow@webdev.ines.ro cc: gentoo-dev@gentoo.org In-Reply-To: <1066286611.5224.13.camel@localhost> Message-ID: References: <1066286611.5224.13.camel@localhost> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: [gentoo-dev] djbdns 1.05-r8 breaks forward-only behaviour of dnscache X-Archives-Salt: 6437b857-cd89-4774-89b1-db391d87ed3c X-Archives-Hash: baa85d2d2bc2aba2563303e163ad1ccb Phew... I've noticed there was something wrong with djbdns, but I couldn't figure out why queries take so much time after the upgrade... thanks. On Thu, 16 Oct 2003, Justin Whitney wrote: > Hi, > > The round-robin patch included in the djbdns-1.05-r8 ebuild breaks > default dnscache FORWARDONLY behaviour. this means that servers/@ and > env/FORWARDONLY are not honored, and the ns roots are queried for > lookups. The result of the patch is that if you set FORWARDONLY and > servers/@ to a non-root cache, expecting to make efficient use of, say, > your ISP's nameservers, you'll end up doing far more queries than you > intended for any given lookup... on my systems because of latency I was > timing out for a lot of lookups. to test, compile with rr-patch, set > dnscache up to do forward-only (per DJB's docs), and then sniff to see > the root queries I mentioned. recompile without it, and repeat to see > the difference. > > bug filed. > > --Justin Whitney > > -- > gentoo-dev@gentoo.org mailing list > > -- gentoo-dev@gentoo.org mailing list