Date: Sun, 27 Jan 2008 22:21:16 -0800 From: Doug Barton <dougb@FreeBSD.org> To: Hartmut Brandt <hartmut.brandt@dlr.de> Cc: Alexander Leidinger <Alexander@Leidinger.net>, current@FreeBSD.org, =?UTF-8?B?RGFnLUVybGlu?=, =?UTF-8?B?ZyBTbcODwrhyZ3Jhdg==?= <des@des.no> Subject: Re: resolver change? Message-ID: <479D745C.3090207@FreeBSD.org> In-Reply-To: <479CFD3B.6020806@dlr.de> References: <86d4rn1kln.fsf@ds4.des.no> <ygeejc3ck1z.wl%ume@mahoroba.org> <86sl0jywii.fsf@ds4.des.no> <yged4rncetu.wl%ume@mahoroba.org> <86abmryun9.fsf@ds4.des.no> <20080127213851.506zunyhwwg4wsgs@webmail.leidinger.net> <479CFD3B.6020806@dlr.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Hartmut Brandt wrote:
> Alexander Leidinger wrote:
>> Quoting Dag-Erling Smørgrav <des@des.no> (from Sun, 27 Jan 2008
>> 19:45:46 +0100):
>>
>>> Hajimu UMEMOTO <ume@mahoroba.org> writes:
>>>> Dag-Erling Smørgrav <des@des.no> 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.
What happens if you disable nscd completely?
Doug
--
This .signature sanitized for your protection
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?479D745C.3090207>