From owner-freebsd-stable@FreeBSD.ORG Fri May 5 07:52:00 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C1F8316A405; Fri, 5 May 2006 07:52:00 +0000 (UTC) (envelope-from freebsd-stable@lists.b0rken.net) Received: from water.b0rken.net (ip-1.b0rken.net [194.7.227.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id CABC843D69; Fri, 5 May 2006 07:51:57 +0000 (GMT) (envelope-from freebsd-stable@lists.b0rken.net) Received: from fire.b0rken.net ([172.16.1.10]) by water.b0rken.net with esmtp (Exim 4.34) id 1Fbv7T-0003SA-Tu; Fri, 05 May 2006 09:53:00 +0200 Received: by fire.b0rken.net (Postfix, from userid 502) id 08B572DB8; Fri, 5 May 2006 09:46:22 +0200 (CEST) Date: Fri, 5 May 2006 09:46:22 +0200 From: Jan Gyselinck To: Hajimu UMEMOTO Message-ID: <20060505094622.B11288@fire.b0rken.net> References: <20060501204640.B8351@fire.b0rken.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.23i X-Mailer: Mutt Cc: Jan Gyselinck , stable@freebsd.org Subject: Re: resolver behaviour regarding searchlist and A/AAAA query replies X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Jan Gyselinck List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 May 2006 07:52:00 -0000 On Fri, May 05, 2006 at 08:38:20AM +0900, Hajimu UMEMOTO wrote: > Hi, > > >>>>> On Mon, 1 May 2006 20:46:40 +0200 > >>>>> Jan Gyselinck said: > > Jan> What I find strange though, is the fact it's now applying the searchlist > Jan> to get an answer on the AAAA query. Other than the fact this could > Jan> potentially give unpredictable results in specific situations, I find > Jan> this rather illogical. Since one of the queries (A or AAAA) succeeded > Jan> we _know_ the host in question exists (and the searchlist is there to > Jan> make non-fqdn queries work for 'local' hosts, by applying the searchlist > Jan> if the host does not seem to exist). So, in short, isn't this a bug? > > Which application did you use? The application which doesn't use > getaddrinfo(3) has this issue, and it cannot be fixed without > re-writing the application to use getaddrinfo(3). konqueror, which is dogslow on this box, there must be something else playing here too... Jan Gyselinck