logging config no longer working as expected
Mark Andrews
Mark_Andrews at isc.org
Fri Jan 19 22:49:02 UTC 2007
> Thanks! So in relation to my other question about SERVFAIL messages, which
> category do those fall into? I tried "resolver" but it didn't work. This DNS
> server is optioned to forward-only, if it matters.
Named can report the category of any log message. You just need
to adjust the channel parameters to report the category.
print-category yes;
Mark
> -----Original Message-----
> From: Mark_Andrews at isc.org [mailto:Mark_Andrews at isc.org]
> Sent: Thursday, January 18, 2007 4:33 PM
> To: Michael Bernhardt
> Cc: bind-users at isc.org
> Subject: Re: logging config no longer working as expected
>
>
> > I'm running 9.3.3. We have a lot of windows clients who are occasionally
> > trying to register with our internal name servers. As I don't care and
> don't
> > need to know, I had the following implemented in BIND 9.2.3 and it worked,
> > but now it doesn't and I see the complaints again in var/log/messages
> about
> > denied updates.
> >
> >
> > logging {
> > // ignore all "client" errors-- failed dynamic updates, etc.
> > category client { "null"; };
> > };
> >
> > Is there a change in syntax I need to make and if not, what's going on?
> > Thanks in advance!
>
> 1301. [func] New category 'update-security'.
> --
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742 INTERNET: Mark_Andrews at isc.org
>
>
>
>
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: Mark_Andrews at isc.org
More information about the bind-users
mailing list