From owner-freebsd-current@FreeBSD.ORG Sun Jan 27 18:48:27 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 14FDF16A468 for ; Sun, 27 Jan 2008 18:48:27 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id D656413C45B for ; Sun, 27 Jan 2008 18:48:26 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 958B84AE78; Sun, 27 Jan 2008 13:48:25 -0500 (EST) Date: Sun, 27 Jan 2008 18:48:25 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= In-Reply-To: <86abmryun9.fsf@ds4.des.no> Message-ID: <20080127184656.B60477@fledge.watson.org> References: <86d4rn1kln.fsf@ds4.des.no> <86sl0jywii.fsf@ds4.des.no> <86abmryun9.fsf@ds4.des.no> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="621616949-245006364-1201459705=:60477" Cc: 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 18:48:27 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --621616949-245006364-1201459705=:60477 Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE On Sun, 27 Jan 2008, Dag-Erling Sm=F8rgrav wrote: > Hajimu UMEMOTO writes: >> Dag-Erling Sm=F8rgrav writes: >>> OK, so the resolver now uses a process-internal cache? Is there any wa= y=20 >>> 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= =20 > 13, so something broke between then and January 21. A casual glance suggests no pertinent changes in that timeframe -- however,= =20 were you just updating your kernel, or also userspace, and in particular,= =20 libc? > My name server does *not* forward queries, it goes straight to the source= =2E=20 > Everything looks fine if I run host(1) multiple times, it only seems to f= ail=20 > when successive lookups are made from the same process. What happens if you back out getaddrinfo.c:1.86: ---------------------------- revision 1.86 date: 2007/09/05 18:08:14; author: jinmei; state: Exp; lines: +19 -2 ensure the head entry of addrinfo chain has non-NULL ai_canonname to be compliant with RFC3493. PR: standards/114910 Approved by: ume (mentor) Approved by: re MFC after: 1 week ---------------------------- Robert N M Watson Computer Laboratory University of Cambridge --621616949-245006364-1201459705=:60477--