From owner-freebsd-security Wed Jun 16 4:17:44 1999 Delivered-To: freebsd-security@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 60B6B14E45 for ; Wed, 16 Jun 1999 04:17:41 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id NAA10183; Wed, 16 Jun 1999 13:17:01 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: dan.langille@dvl-software.com Cc: Dag-Erling Smorgrav , security@FreeBSD.ORG, Mike Nowlin Subject: Re: named timeouts In-reply-to: Your message of "Wed, 16 Jun 1999 23:12:21 +1200." <199906161112.GAA26982@metis.host4u.net> Date: Wed, 16 Jun 1999 13:17:01 +0200 Message-ID: <10181.929531821@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <199906161112.GAA26982@metis.host4u.net>, "Dan Langille" writes: >> > $ tail kernel.log >> > Jun 16 09:16:42 ns /kernel: Connection attempt to UDP 127.0.0.1:1391 >> > from 127.0.0.1:53 Jun 16 09:17:02 ns /kernel: Connection attempt to UDP >> > 127.0.0.1:1393 from 127.0.0.1:53 >> >> Ah, these are log_in_vain messages. What they mean is that named isn't >> listening on 127.0.0.1. You need to add localhost or localnets to the >> allow-query clause in named.conf (either in the options section or in each >> zone). Actually it doesnt, it means that the client closed his socket before named got to answer... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message