Maintained by: NLnet Labs

[Unbound-users] Release 0.7.2

Alexander Gall
Wed Jan 30 16:50:14 CET 2008

On Wed, 30 Jan 2008 15:48:35 +0100, "W.C.A. Wijngaards" <wouter at> said:

> | In general, what I would find exetremely useful (and what I've been
> | missing so much with BIND) is a catalog of log messages, possibly
> | including additional information what events can cause a message to be
> | generated.  If you're going to do this, please add unique tags for
> | every message, so you can change the message text in later releases
> | but still identify the message itself.
> |
> | I have this Perl script that analyzes my BIND logs and I have to
> | change it with every release of BIND because they often change the
> | message texts.

> Nice idea. Some type names and a verbosity value for each.
> I'll think about it. It would mean a bit of a revision of the logging
> system.

> The trouble is keeping such a catalog up to date. Maybe
> source-code-annotation can help here :-)

Yes, that would sound like a good way to do it.  I think that would be
a cool thing to have.  It would also keep down the volume on this list
once unbound is taking off big time, because people would actually
understand what the software is telling them :-)