[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: log_rdns.patch

To: Michael Str??der <michael@stroeder.com>
Subject: Re: log_rdns.patch
From: Brian Reichert <reichert@numachi.com>
Date: Wed, 9 Mar 2016 09:59:52 -0500
Cc: openldap-technical@openldap.org, "A. Schulze" <sca@andreasschulze.de>
Content-disposition: inline
In-reply-to: <56E03790.60603@stroeder.com>
References: <20160309084606.Horde.OodXAnyIQ1UBYxv8NgbYcyH@andreasschulze.de> <56DFD95B.5080508@symas.com> <56DFFE2B.2030103@stroeder.com> <20160309140529.Horde.vAcXEiI2ao2XRA3zxjfeGBP@andreasschulze.de> <56E03790.60603@stroeder.com>
User-agent: Mutt/1.5.9i

On Wed, Mar 09, 2016 at 03:47:44PM +0100, Michael Str??der wrote:
> As Howard already said:
> Use a decent logfile post-processor before looking at the log file.

But, what if PTR records have changed between when the log entry is
written, and it's analysis?

In my own opinion, if you're not running a public server, but one
within your company's LAN, then the set of hostnames won't be as
numerous, nor as fluid, so I suspect descent resolver could cope.

I agree that such a feature on a public server would not fare well.

> Ciao, Michael.

-- 
Brian Reichert				<reichert@numachi.com>
BSD admin/developer at large

Follow-Ups:
- Re: log_rdns.patch
  - From: Michael Ströder <michael@stroeder.com>

References:
- log_rdns.patch
  - From: "A. Schulze" <sca@andreasschulze.de>
- Re: log_rdns.patch
  - From: Howard Chu <hyc@symas.com>
- Re: log_rdns.patch
  - From: Michael Ströder <michael@stroeder.com>
- Re: log_rdns.patch
  - From: "A. Schulze" <sca@andreasschulze.de>
- Re: log_rdns.patch
  - From: Michael Ströder <michael@stroeder.com>

Prev by Date: Re: log_rdns.patch
Next by Date: Re: log_rdns.patch
Index(es):
- Chronological
- Thread