"Hipolito A. Gonzalez M." wrote:
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
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:
-- -ashley One of these days I'm going to completely organize my life.
* Ashley (ashleyg@dnai.com) [010404 12:28]:
Can anyone tell me why SuSE set up bind8 logging in this way?
Isn't bind chroot'ed in 7.1? If so, named wouldn't have access to the /dev/log socket so it wouldn't make sense to have any entries in /etc/syslogd.conf for it. I guess I should get around to installing 7.1 someday ;) -- -ckm
Not by default. Take a look at marc's secure-compartment. Really he is good: www.suse.de/~marc -> 'Work at SuSE' -> Compartment. His init_bind8 script works like magic, however slave servers need to have the binary that does zone transfers ( something-xfer, I forget) added to the list of files to go into the chroot jail. On Wed, Apr 04, 2001 at 12:55:05PM -0700, Christopher Mahmood wrote:
-- -ashley One of these days I'm going to completely organize my life.
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:
-- -ashley One of these days I'm going to completely organize my life.
* Ashley (ashleyg@dnai.com) [010404 12:28]:
Can anyone tell me why SuSE set up bind8 logging in this way?
Isn't bind chroot'ed in 7.1? If so, named wouldn't have access to the /dev/log socket so it wouldn't make sense to have any entries in /etc/syslogd.conf for it. I guess I should get around to installing 7.1 someday ;) -- -ckm
Not by default. Take a look at marc's secure-compartment. Really he is good: www.suse.de/~marc -> 'Work at SuSE' -> Compartment. His init_bind8 script works like magic, however slave servers need to have the binary that does zone transfers ( something-xfer, I forget) added to the list of files to go into the chroot jail. On Wed, Apr 04, 2001 at 12:55:05PM -0700, Christopher Mahmood wrote:
-- -ashley One of these days I'm going to completely organize my life.
participants (3)
-
Ashley -
Christopher Mahmood -
Emmerich Eggler