From owner-freebsd-current@FreeBSD.ORG Mon Jan 28 09:08: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 ED46916A419 for ; Mon, 28 Jan 2008 09:08: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 C2A4C13C4DB for ; Mon, 28 Jan 2008 09:08:27 +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 F2E724CCA8; Mon, 28 Jan 2008 04:08:26 -0500 (EST) Date: Mon, 28 Jan 2008 09:08:26 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= In-Reply-To: <86ir1eye24.fsf@ds4.des.no> Message-ID: <20080128090552.B14807@fledge.watson.org> References: <86d4rn1kln.fsf@ds4.des.no> <86sl0jywii.fsf@ds4.des.no> <86abmryun9.fsf@ds4.des.no> <20080127184656.B60477@fledge.watson.org> <86myqrxaw3.fsf@ds4.des.no> <20080127204825.J71547@fledge.watson.org> <86ir1eye24.fsf@ds4.des.no> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="621616949-1775755244-1201511306=:14807" 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: Mon, 28 Jan 2008 09:08:28 -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-1775755244-1201511306=:14807 Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE On Mon, 28 Jan 2008, Dag-Erling Sm=F8rgrav wrote: > Robert Watson writes: >> On the grounds that paranoia is clearly better, my suggestion at this po= int=20 >> would be to run tcpdump between the caching resolver and ntpd and see wh= at=20 >> is actually going on the wire. > > In this case, they're on the same machine. I'm not sure how well tcpdump= =20 > works on loopback devices... It should work just fine. Make sure to use -vvv so you get all the details= =2E >> The name server should be rotating them in reply, and it would be good t= o=20 >> confirm that it's doing that. > > The results from host(1) seem to indicate that it does. > >> It would also be good to check that it's looking up what you think it's= =20 >> looking up, and indeed, what it should be looking at. > > Not sure what you mean by this... I'm sure I don't have to tell you that when debugging, it's good to look un= der=20 the hood to see what's actually happening, as one misunderstanding can wast= e=20 hours of time chasing the wrong lead. Robert N M Watson Computer Laboratory University of Cambridge --621616949-1775755244-1201511306=:14807--