From owner-freebsd-security Wed Jun 16 4:59:54 1999 Delivered-To: freebsd-security@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id D5CD01523B for ; Wed, 16 Jun 1999 04:59:50 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.1) id NAA82599; Wed, 16 Jun 1999 13:56:43 +0200 (CEST) (envelope-from des) To: Poul-Henning Kamp Cc: dan.langille@dvl-software.com, Dag-Erling Smorgrav , security@FreeBSD.ORG, Mike Nowlin Subject: Re: named timeouts References: <10181.929531821@critter.freebsd.dk> From: Dag-Erling Smorgrav Date: 16 Jun 1999 13:56:42 +0200 In-Reply-To: Poul-Henning Kamp's message of "Wed, 16 Jun 1999 13:17:01 +0200" Message-ID: Lines: 16 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Poul-Henning Kamp writes: > > > > 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... Doh! I inverted 'to' and 'from' in my head. Am I the only one to expect 'from' to come before 'to'? DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message