named and DNSSEC

Hello,

I'm one of the developers on the DNSSEC-Tools project, and our DNSSEC
config is included in logwatch (dnssec and resolver). The team member
who originally submitted these files in 2005 is gone, and we are trying
to figure out why the dnssec and resolver configuration was separate
from named. In the current setup, the named config ignores DNSSEC
related messages, and the user must configure named logging to put
DNSSEC messages into their own log file for the dnssec logwatch config
to be useful.

We also found that RedHat is patching fedora to add DNSSEC message
handling directly in the named logwatch config for their rpm package.
[See https://bugzilla.redhat.com/show_bug.cgi?id=666394]. I'd bet they
are going to want to push their changes upstream.

By default named does all it's logging via syslog, and I don't think
most folks will think to look for a logwatch config for it other than
the existing named config. So it seems to me that it would make sense to
merge our pattern updates with RedHat's, into the named config, and do
away with the dnssec and resolver logwatch configs.

What do you guys think about it?

Robert
--
Senior Software Engineer
SPARTA (dba Cobham Analytic Solutions)

------------------------------------------------------------------------------
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
The must-attend event for mobile developers. Connect with experts. 
Get tools for creating Super Apps. See the latest technologies.
Sessions, hands-on labs, demos & much more. Register early & save!
http://p.sf.net/sfu/rim-blackberry-1

_______________________________________________
Logwatch-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/logwatch-devel

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)

iEYEARECAAYFAk45kXUACgkQ7/fVLLY1mnhCAgCfaRmbpCrpMsmPNHvYnZUrLOAz
pOIAn33M5cSu0BVrxusnUOeCJqZDXuG6
=5eXk
-----END PGP SIGNATURE-----