Keep "starting BIND 9.1.0" out of syslog?

Lou Goddard lgoddard at
Sat Dec 11 15:52:32 UTC 2004

Edit main.c.

"main.c:               ISC_LOG_NOTICE, "starting BIND %s%s", =

-----Original Message-----
From: bind-users-bounce at [mailto:bind-users-bounce at]On
Behalf Of Barry Margolin
Sent: Friday, December 10, 2004 11:02 PM
To: comp-protocols-dns-bind at
Subject: Re: Keep "starting BIND 9.1.0" out of syslog?

In article <cpda2v$1vhi$1 at>, Pete Ehlke <pde at>=20

> On Fri Dec 10, 2004 at 13:44:04 -0800, george_jenior at wrote:
> >We're running BIND 9.1.0. There is a requirement to not have the BIND
> >version logged to syslog. (But they still want other messages to go =
> >syslog.)
> >
> Assuming that this 'requirement' comes from your security group, their
> priorities are severely misplaced. You're running a significantly
> outdated version of BIND will well-known and serious bugs.=20
> Update to a current version, and trust the people who can read your
> system logs.=20

While that may be a good idea, do you really think it will solve the=20
logging problem?

I expect that the reason why this message isn't affected by the logging=20
configuration in named.conf is because it's logged as soon as named=20
starts up, *before* it starts reading the configuration file.  So it=20
can't possibly be affected by that file.

Barry Margolin, barmar at
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***

More information about the bind-users mailing list