Date: Sun, 27 Jan 2008 20:49:47 +0000 (GMT) From: Robert Watson <rwatson@FreeBSD.org> To: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> Cc: current@FreeBSD.org Subject: Re: resolver change? Message-ID: <20080127204825.J71547@fledge.watson.org> In-Reply-To: <86myqrxaw3.fsf@ds4.des.no> 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>
index | next in thread | previous in thread | raw e-mail
On Sun, 27 Jan 2008, Dag-Erling Smørgrav wrote: > Robert Watson <rwatson@FreeBSD.org> writes: > >> A casual glance suggests no pertinent changes in that timeframe -- however, >> were you just updating your kernel, or also userspace, and in particular, >> libc? > > No, this is the weird thing. > > I'm starting to think I'm imagining it all... > > But this *definitely* worked correctly on January 13, and *definitely* > didn't work correctly on January 21, nor does it work correctly today. > >> What happens if you back out getaddrinfo.c:1.86: > > I've been running with that version of getaddrinfo.c since long before it > stopped working. 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. The name server should be rotating them in reply, and it would be good to confirm that it's doing that. 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. Robert N M Watson Computer Laboratory University of Cambridgehelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080127204825.J71547>