Date: Tue, 24 Oct 2006 23:24:06 +0800 From: "Jiawei Ye" <leafy7382@gmail.com> To: "Hajimu UMEMOTO" <ume@freebsd.org> Cc: Doug Barton <dougb@freebsd.org>, Kris Kennaway <kris@obsecurity.org>, nork@freebsd.org, "Simon L. Nielsen" <simon@freebsd.org>, freebsd-current@freebsd.org, Joel@freebsd.org, Ion-Mihai IOnut Tetcu <itetcu@freebsd.org> Subject: Re: Resolver not always resolving hostnames Message-ID: <c21e92e20610240824n7e94e4c1jf454697cab4120a9@mail.gmail.com> In-Reply-To: <ygehcxtkaig.wl%ume@mahoroba.org> References: <20061022095811.GA10743@zaphod.nitro.dk> <200610221423.19817.andy@athame.co.uk> <453BFC2A.5010501@FreeBSD.org> <20061023022928.35b7b23c@it.buh.tecnik93.com> <c21e92e20610231850p368221cfx13b107cc6939b4ab@mail.gmail.com> <20061024021919.GA74370@xor.obsecurity.org> <c21e92e20610231924r6d5029d9wc0bacc5a7a5a4078@mail.gmail.com> <453D9B3B.5090000@FreeBSD.org> <c21e92e20610240641k417dd148q333dd75d8478c459@mail.gmail.com> <ygehcxtkaig.wl%ume@mahoroba.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10/24/06, Hajimu UMEMOTO <ume@freebsd.org> wrote: > leafy7382> This is much better. It would be great if this is commited. > > I've committed it into 7-CURRENT, and I'll MFC it into RELENG_6 after > 3 days. > > The fix should help in certain case. However, it seems doesn't help > for nork-san's case. He could reproduce it, and sent me his ktrace > output. As far as I can see his output, his local name server (BIND > 9.3.2-P1) returned the response with no answer record. As a result, > his csup ended up with following error: > > Name lookup failure for "cvsup.jp.freebsd.org": hostname nor > servname provided, or not known > > I suspect that the BIND9's named have some problem. > > "Name lookup failure for "cvsup.jp.freebsd.org": hostname nor servname \ > provided, or not known > " > Sincerely, > > -- > Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan You are correct, I just ran into that a few times in the last hour. But it is a lot less frequent than before. I also run a local BIND9 for our company. I think some commits happening after between Sept 30 and Oct 15th caused it, because I did not see such symptom before late Sept and I rebuilt my system around mid Oct. Best regards, Jiawei -- "If it looks like a duck, walks like a duck, and quacks like a duck, then to the end user it's a duck, and end users have made it pretty clear they want a duck; whether the duck drinks hot chocolate or coffee is irrelevant."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c21e92e20610240824n7e94e4c1jf454697cab4120a9>