Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 16 Jun 1999 16:28:20 +0000 (GMT)
From:      "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com>
To:        des@flood.ping.uio.no (Dag-Erling Smorgrav)
Cc:        phk@critter.freebsd.dk (Poul-Henning Kamp), dan.langille@dvl-software.com, security@FreeBSD.ORG, mike@argos.org (Mike Nowlin)
Subject:   Re: named timeouts
Message-ID:  <199906161628.JAA57891@gndrsh.aac.dev.com>
In-Reply-To: <xzpyahkcq9x.fsf@flood.ping.uio.no> from Dag-Erling Smorgrav at "Jun 16, 1999 01:56:42 pm"

next in thread | previous in thread | raw e-mail | index | archive | help
> Poul-Henning Kamp <phk@critter.freebsd.dk> 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'?

No, infact I meant to ask that this be changed a long time ago, but I ended up turing
of log_in_vain messages so I forgot to ever get it fixed.

Could someone please make the necessary commits to -current and -stable...


-- 
Rod Grimes - KD7CAX - (RWG25)                    rgrimes@gndrsh.dnsmgr.net


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?199906161628.JAA57891>