Date: Wed, 16 Jun 1999 23:27:43 +1200 From: "Dan Langille" <junkmale@xtra.co.nz> To: security@FreeBSD.ORG Cc: Dag-Erling Smorgrav <des@flood.ping.uio.no>, Poul-Henning Kamp <phk@critter.freebsd.dk> Subject: Re: named timeouts Message-ID: <19990616113019.HOKO311284.mta2-rme@wocker> In-Reply-To: <10181.929531821@critter.freebsd.dk> References: 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
On 16 Jun 99, at 13:17, Poul-Henning Kamp wrote: > 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... OK. Now we're back to my initial theory. How do I increase the time the client keeps the socket open? Or is that something possible to configure? -- Dan Langille - DVL Software Limited The FreeBSD Diary - http://www.FreeBSDDiary.org/freebsd/ NZ FreeBSD User Group - http://www.nzfug.nz.freebsd.org/ The Racing System - http://www.racingsystem.com/racingsystem.htm 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?19990616113019.HOKO311284.mta2-rme>