From owner-freebsd-hackers Mon Jan 6 4:50:44 2003 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 00C8537B401 for ; Mon, 6 Jan 2003 04:50:42 -0800 (PST) Received: from straylight.ringlet.net (office.sbnd.net [217.75.140.130]) by mx1.FreeBSD.org (Postfix) with SMTP id 8588943EC5 for ; Mon, 6 Jan 2003 04:50:32 -0800 (PST) (envelope-from roam@ringlet.net) Received: (qmail 986 invoked by uid 1000); 6 Jan 2003 12:49:46 -0000 Date: Mon, 6 Jan 2003 14:49:46 +0200 From: Peter Pentchev To: lemon Cc: freebsd-hackers@freebsd.org Subject: Re: getnameinfo contacting 'wrong' resolver for lookup Message-ID: <20030106124946.GA384@straylight.oblivion.bg> Mail-Followup-To: lemon , freebsd-hackers@freebsd.org References: <3E182B54.4090007@aldigital.co.uk> <20030106101505.GC382@straylight.oblivion.bg> <3E197779.3040706@aldigital.co.uk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="BOKacYhQ+x31HxR3" Content-Disposition: inline In-Reply-To: <3E197779.3040706@aldigital.co.uk> User-Agent: Mutt/1.5.3i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --BOKacYhQ+x31HxR3 Content-Type: text/plain; charset=windows-1251 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jan 06, 2003 at 12:32:57PM +0000, lemon wrote: > Peter Pentchev wrote: > >On Sun, Jan 05, 2003 at 12:55:48PM +0000, lemon wrote: > > > >> > >># tcpdump -ni lo0 > >>tcpdump: listening on lo0 > >> > >>[ 'wrong' listener being contacted ] > >> > >>18:02:38.448117 192.168.1.2.1226 > 192.168.1.2.53: > >> 24805+ PTR? 7.57.192.80.in-addr.arpa. (42) > >>18:02:43.452867 192.168.1.2.1227 > 192.168.1.2.53: > >> 24805+ PTR? 7.57.192.80.in-addr.arpa. (42) > >>18:02:53.462937 192.168.1.2.1228 > 192.168.1.2.53: > >> 24805+ PTR? 7.57.192.80.in-addr.arpa. (42) > >>18:03:13.473076 192.168.1.2.1229 > 192.168.1.2.53: > >> 24805+ PTR? 7.57.192.80.in-addr.arpa. (42) > > > > > >Are you sure those connections are from the SSH daemon, and not from the > >dnscache itself? >=20 > i believe they're from sshd, yes. i'm not seeing any prior activity from= =20 > the dnscache before the external tinydns is contacted. >=20 > > > >Can you post the full configuration of the tinydns and dnscache > >services, e.g. using Jonathan de Boyne Pollard's tinydns-showctl and > >dnscache-showctl utilities, available from > >http://homepages.tesco.net/~J.deBoynePollard/Softwares/djbdns.html > >Also, it would be very useful to see the full logfiles generated by > >dnscache and tinydns around the time of the unsuccessful lookups, and > >the exact contents of your /etc/resolv.conf file. >=20 > sure, inline below. if it borks the mailer, it's also at: > . Mmm.. it seems that I might need a bit more info to diagnose the problem. Could you also post the output of the following command: grep ^ /var/dnscache/root/servers/* > the two log tails were started at the same time, but the activity was=20 > seen in the tinydns log first, then the dnscache. Well, those log snippets do not seem to cover the same time interval. Running them through the tai64nlocal utility shows that the tinydns log entries are from 13:04:29 to 13:04:59, while the dnscache ones start at 13:05:39. Are there any dnscache log entries for 13:03 or 13:04? G'luck, Peter --=20 Peter Pentchev roam@ringlet.net roam@FreeBSD.org PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 This sentence is false. --BOKacYhQ+x31HxR3 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+GXtq7Ri2jRYZRVMRApwgAKCIZ16149LP4jTp6Lj27XnHlzeP7ACeLm2/ sd4xrTOFTjg1knKnCtFPJuw= =+pZi -----END PGP SIGNATURE----- --BOKacYhQ+x31HxR3-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message