Date: Wed, 16 Jun 1999 13:20:52 -0600 From: Warner Losh <imp@harmony.village.org> To: Dag-Erling Smorgrav <des@flood.ping.uio.no> Cc: junkmale@xtra.co.nz, security@FreeBSD.ORG, Mike Nowlin <mike@argos.org> Subject: Re: named timeouts Message-ID: <199906161920.NAA01054@harmony.village.org> In-Reply-To: Your message of "16 Jun 1999 12:59:38 %2B0200." <xzpzp20csx1.fsf@flood.ping.uio.no> References: <xzpzp20csx1.fsf@flood.ping.uio.no> "Dan Langille"'s message of "Wed, 16 Jun 1999 07:45:31 %2B1200" <19990616100254.GZCQ311284.mta2-rme@wocker>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <xzpzp20csx1.fsf@flood.ping.uio.no> Dag-Erling Smorgrav writes: : 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). This is not necessarily correct. I have log in vain set on my machine and I get them sometimes. I've been able to recreate this problem by looking up a previously unknown DNS entry. This causes a query to go out to the big bad internet. In the mean while, the DNS client times out and closes the socket it was listening for its answer on. A short time later, the answer comes back. The packet is tossed and logged. When the client and server are the same machine, this can cause confusion. Warner 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?199906161920.NAA01054>