I discoverd (the hard way) in SuSE 7.1 the /etc/named.conf file by default does not log anything of category 'default', which is basically everything you are trying to log. Comment out the appropriate line and syslog will get bind8 messages as it should: In /etc/named.conf: # # do not be verbose about these problems... # logging { # category default { null; }; ### comment out this line ### category lame-servers { null; }; category cname { null; }; }; Can anyone tell me why SuSE set up bind8 logging in this way? On Tue, Apr 03, 2001 at 07:10:20PM +0200, Emmerich Eggler wrote:

"Hipolito A. Gonzalez M." wrote:

...

emm@eggler.ch wrote:

...

At Mon, 2 Apr 2001 15:19:38 +0200 , "Reckhard, Tobias" wrote:

...

Check out the contents of /usr/share/doc/packages/bind8. BIND's logging config is way beyond the scope of this list.

sure. but it's no secret and trivial: named -d 9 starts bind the noisy way.

Thank you my friend, but, where is stored the log? In /var/log/messages nothing appear.

is your syslog running? do you have any __explicit__ log configuration (other than syslog) in your named.boot?

as far as i know, suse's named logs via syslog. if yours isn't, than it might mean:

a) you are not using suse's named/syslog combination b) your syslog is not started c) you changed "something" on your host's config

regards emmerich

--------------------------------------------------------------------- To unsubscribe, e-mail: suse-security-unsubscribe@suse.com For additional commands, e-mail: suse-security-help@suse.com

-- -ashley One of these days I'm going to completely organize my life.