Date: Wed, 16 Jun 1999 13:17:01 +0200 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: dan.langille@dvl-software.com Cc: Dag-Erling Smorgrav <des@flood.ping.uio.no>, security@FreeBSD.ORG, Mike Nowlin <mike@argos.org> Subject: Re: named timeouts Message-ID: <10181.929531821@critter.freebsd.dk> In-Reply-To: Your message of "Wed, 16 Jun 1999 23:12:21 %2B1200." <199906161112.GAA26982@metis.host4u.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?10181.929531821>