resolver change?

Doug Barton dougb at
Sun Jan 27 22:47:58 PST 2008

Hartmut Brandt wrote:
> Alexander Leidinger wrote:
>> Quoting Dag-Erling Smørgrav <des at> (from Sun, 27 Jan 2008
>> 19:45:46 +0100):
>>> Hajimu UMEMOTO <ume at> writes:
>>>> Dag-Erling Smørgrav <des at> 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?



    This .signature sanitized for your protection

More information about the freebsd-current mailing list