Date: Sun, 27 Jan 2008 19:45:46 +0100 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> To: Hajimu UMEMOTO <ume@mahoroba.org> Cc: current@FreeBSD.org Subject: Re: resolver change? Message-ID: <86abmryun9.fsf@ds4.des.no> In-Reply-To: <yged4rncetu.wl%ume@mahoroba.org> (Hajimu UMEMOTO's message of "Mon\, 28 Jan 2008 03\:18\:21 %2B0900") References: <86d4rn1kln.fsf@ds4.des.no> <ygeejc3ck1z.wl%ume@mahoroba.org> <86sl0jywii.fsf@ds4.des.no> <yged4rncetu.wl%ume@mahoroba.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hajimu UMEMOTO <ume@mahoroba.org> writes: > Dag-Erling Sm=C3=B8rgrav <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. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86abmryun9.fsf>