From owner-freebsd-current@FreeBSD.ORG Thu Oct 26 18:22:14 2006 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EEA0B16A47E; Thu, 26 Oct 2006 18:22:13 +0000 (UTC) (envelope-from hrs@FreeBSD.org) Received: from mail.allbsd.org (vlsi00.si.noda.tus.ac.jp [133.31.130.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id E46AB43D8D; Thu, 26 Oct 2006 18:22:04 +0000 (GMT) (envelope-from hrs@FreeBSD.org) Received: from delta.allbsd.org (p2118-ipbf608funabasi.chiba.ocn.ne.jp [125.175.93.118]) (authenticated bits=128) by mail.allbsd.org (8.13.1/8.13.4) with ESMTP id k9QIJ0dH084207; Fri, 27 Oct 2006 03:19:13 +0900 (JST) (envelope-from hrs@FreeBSD.org) Received: from localhost (alph.allbsd.org [192.168.0.10]) (authenticated bits=0) by delta.allbsd.org (8.13.4/8.13.4) with ESMTP id k9QIIOUj027221; Fri, 27 Oct 2006 03:18:26 +0900 (JST) (envelope-from hrs@FreeBSD.org) Date: Fri, 27 Oct 2006 02:56:00 +0900 (JST) Message-Id: <20061027.025600.59733168.hrs@allbsd.org> To: leafy7382@gmail.com From: Hiroki Sato In-Reply-To: References: X-PGPkey-fingerprint: BDB3 443F A5DD B3D0 A530 FFD7 4F2C D3D8 2793 CF2D X-Mailer: Mew version 5.1 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Multipart/Signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="--Security_Multipart(Fri_Oct_27_02_56_00_2006_818)--" Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.88.2, clamav-milter version 0.88.2 on gatekeeper.allbsd.org X-Virus-Status: Clean X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (mail.allbsd.org [133.31.130.32]); Fri, 27 Oct 2006 03:19:14 +0900 (JST) Cc: dougb@FreeBSD.org, ume@FreeBSD.org, Joel@FreeBSD.org, nork@FreeBSD.org, simon@FreeBSD.org, freebsd-current@FreeBSD.org, kris@obsecurity.org, itetcu@FreeBSD.org Subject: Re: Resolver not always resolving hostnames 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: Thu, 26 Oct 2006 18:22:14 -0000 ----Security_Multipart(Fri_Oct_27_02_56_00_2006_818)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit "Jiawei Ye" wrote in : le> On 10/24/06, Hajimu UMEMOTO wrote: le> > leafy7382> This is much better. It would be great if this is commited. le> > le> > I've committed it into 7-CURRENT, and I'll MFC it into RELENG_6 after le> > 3 days. le> > le> > The fix should help in certain case. However, it seems doesn't help le> > for nork-san's case. He could reproduce it, and sent me his ktrace le> > output. As far as I can see his output, his local name server (BIND le> > 9.3.2-P1) returned the response with no answer record. As a result, le> > his csup ended up with following error: le> > le> > Name lookup failure for "cvsup.jp.freebsd.org": hostname nor le> > servname provided, or not known le> > le> > I suspect that the BIND9's named have some problem. le> > le> > "Name lookup failure for "cvsup.jp.freebsd.org": hostname nor servname \ le> > provided, or not known le> > " le> > Sincerely, le> > le> > -- le> > Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan le> You are correct, I just ran into that a few times in the last hour. le> But it is a lot less frequent than before. I also run a local BIND9 le> for our company. I think some commits happening after between Sept 30 le> and Oct 15th caused it, because I did not see such symptom before late le> Sept and I rebuilt my system around mid Oct. According to log files on my public cvsup server which is suffering from this problem, this happened on 22 September at least. I have not looked into the source files closely yet, but is it possible that the 9.3.2-P1 patch has a bug that can return 0/0/0 with NOERROR answer packet? I confirmed that behaviors of 4.x's resolver and 6.x's against such a malformed packet are the same, so I think it is not likely a bug in the resolver. -- | Hiroki SATO ----Security_Multipart(Fri_Oct_27_02_56_00_2006_818)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBFQPayTyzT2CeTzy0RAr7xAJ4jMCI1Qw1Uan2np1vCeR37PlcxzQCgiXxZ XxIDFMuHYvw0PpWLEDr+W5I= =Qpjj -----END PGP SIGNATURE----- ----Security_Multipart(Fri_Oct_27_02_56_00_2006_818)----