From owner-freebsd-current@FreeBSD.ORG Sun Jan 27 22:06:19 2008 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1E97616A420 for ; Sun, 27 Jan 2008 22:06:19 +0000 (UTC) (envelope-from Hartmut.Brandt@dlr.de) Received: from smtp-1.dlr.de (smtp-1.dlr.de [195.37.61.185]) by mx1.freebsd.org (Postfix) with ESMTP id AAB2D13C447 for ; Sun, 27 Jan 2008 22:06:18 +0000 (UTC) (envelope-from Hartmut.Brandt@dlr.de) Received: from [129.247.12.10] ([129.247.12.10]) by smtp-1.dlr.de with Microsoft SMTPSVC(6.0.3790.1830); Sun, 27 Jan 2008 22:53:00 +0100 Message-ID: <479CFD3B.6020806@dlr.de> Date: Sun, 27 Jan 2008 22:52:59 +0100 From: Hartmut Brandt Organization: German Aerospace Center User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: Alexander Leidinger References: <86d4rn1kln.fsf@ds4.des.no> <86sl0jywii.fsf@ds4.des.no> <86abmryun9.fsf@ds4.des.no> <20080127213851.506zunyhwwg4wsgs@webmail.leidinger.net> In-Reply-To: <20080127213851.506zunyhwwg4wsgs@webmail.leidinger.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-OriginalArrivalTime: 27 Jan 2008 21:53:01.0024 (UTC) FILETIME=[FC5A8600:01C8612E] Cc: =?UTF-8?B?RGFnLUVybGluZyBTbcODwrhyZ3Jhdg==?= , current@FreeBSD.org Subject: Re: resolver change? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2008 22:06:19 -0000 Alexander Leidinger wrote: > Quoting Dag-Erling Smørgrav (from Sun, 27 Jan 2008 > 19:45:46 +0100): > >> Hajimu UMEMOTO writes: >>> Dag-Erling Smørgrav writes: >>> > OK, so the resolver now uses a process-internal cache? Is there >>> any way >>> > to turn it off? >>> No, our resolver doesn't have a process-internal cache at all. >> >> So what's going on? >> >> Looking back through my logs, it was working correctly as late as >> January 13, so something broke between then and January 21. >> >> My name server does *not* forward queries, it goes straight to the >> source. Everything looks fine if I run host(1) multiple times, it only >> seems to fail when successive lookups are made from the same process. > > Are you seeing this with or without activated nscd/cached? I see the same effect as DES. Tried to disable hosts caching in nscd. Didn't change anything. harti