Date: Mon, 28 Jan 2008 01:44:03 +0100 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> To: Robert Watson <rwatson@FreeBSD.org> Cc: current@FreeBSD.org Subject: Re: resolver change? Message-ID: <86ir1eye24.fsf@ds4.des.no> In-Reply-To: <20080127204825.J71547@fledge.watson.org> (Robert Watson's message of "Sun\, 27 Jan 2008 20\:49\:47 %2B0000 \(GMT\)") References: <86d4rn1kln.fsf@ds4.des.no> <ygeejc3ck1z.wl%ume@mahoroba.org> <86sl0jywii.fsf@ds4.des.no> <yged4rncetu.wl%ume@mahoroba.org> <86abmryun9.fsf@ds4.des.no> <20080127184656.B60477@fledge.watson.org> <86myqrxaw3.fsf@ds4.des.no> <20080127204825.J71547@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Robert Watson <rwatson@FreeBSD.org> writes: > On the grounds that paranoia is clearly better, my suggestion at this > point would be to run tcpdump between the caching resolver and ntpd > and see what is actually going on the wire. In this case, they're on the same machine. I'm not sure how well tcpdump works on loopback devices... > The name server should be rotating them in reply, and it would be good > to 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 looking up, and indeed, what it should be looking at. Not sure what you mean by this... DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86ir1eye24.fsf>