Thanks, maybe I should have asked, what's the difference between default and general. Cheers, Vince
On Tue, Sep 9, 2008 at 12:27 PM, Vinny Abello <[EMAIL PROTECTED]> wrote: > Default is "everything else". If you don't define a category, it will go > to default instead. > > > > -Vinny > > > > *From:* Vincent Poy [mailto:[EMAIL PROTECTED] > *Sent:* Tuesday, September 09, 2008 3:25 PM > *To:* Vinny Abello > *Cc:* [EMAIL PROTECTED]; [email protected] > *Subject:* Re: BIND 9.4.2-P2-W1 stops responding > > > > Yep, that's it. Thanks! Would the default category pretty much send > everything that goes to syslog when nothing for logging is defined? > > > > Cheers, > > Vince > > On Tue, Sep 9, 2008 at 12:19 PM, Vinny Abello <[EMAIL PROTECTED]> wrote: > > I think you're looking for this: > > > > http://www.isc.org/sw/bind/arm94/Bv9ARM.ch06.html#id2574908 > > > > http://www.isc.org/sw/bind/arm94/Bv9ARM.ch06.html#the_category_phrase > > > > > > The channel names are whatever you want to call them. It's the categories > that are predefined. > > > > -Vinny > > > > *From:* Vincent Poy [mailto:[EMAIL PROTECTED] > *Sent:* Tuesday, September 09, 2008 1:55 PM > *To:* Vinny Abello > *Cc:* [EMAIL PROTECTED]; [email protected] > > > *Subject:* Re: BIND 9.4.2-P2-W1 stops responding > > > > Thanks, I have a question. Is there somewhere on the net that has > something explaining the different variables and options for the logging > config since in Unix, everything is sent to the systemlog but with Windows, > it's another story. Also, other than the different filesnames of your > channels, wouldn't the output be identical or does named actually have > defined names of the type which is what the channel names are? Thanks. > > > > Cheers, > > Vince > > > > On Tue, Sep 9, 2008 at 8:05 AM, Vinny Abello <[EMAIL PROTECTED]> wrote: > > We do something like this: > > logging { > channel named_log { > file "c:\bind\log\named.log" versions 3 size 1m; > > severity dynamic; > print-category yes; > print-time yes; > }; > > channel security_log { > file "c:\bind\log\security.log" versions 3 size 1m; > > severity dynamic; > print-category yes; > print-time yes; > }; > > channel update_log { > file "c:\bind\log\update.log" versions 3 size 1m; > > severity dynamic; > print-category yes; > print-time yes; > }; > > channel xfer_log { > file "c:\bind\log\xfer.log" versions 3 size 1m; > > severity dynamic; > print-category yes; > print-time yes; > }; > category default { named_log; }; > > category lame-servers { null; }; > category security { security_log; }; > category update { update_log; }; > category update-security { update_log; }; > category xfer-in { xfer_log; }; > category xfer-out { xfer_log; }; > }; > > > The user created to run named is a standard user by default. Be sure they > have permissions to write to the directory you specify in your > configuration. > > -Vinny > > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > > Behalf Of Vincent Poy > > Sent: Monday, September 08, 2008 12:25 PM > > To: [EMAIL PROTECTED] > > Cc: [email protected] > > Subject: Re: BIND 9.4.2-P2-W1 stops responding > > > > > Speaking about logs using BIND in Windows, how are you guys configuring > > your > > named.conf file because even though I have configured the named.conf as > > follows for logs, the named.log gets created by BIND with 0 bytes but > > has > > remained at 0 bytes ever since. Thanks! > > logging { > > channel named_log { > > file "c:\windows\system32\dns\log\named.log" versions 3 > > size > > 1m; > > severity dynamic; > > print-category yes; > > print-time yes; > > }; > > category default{ > > > }; > > }; > > > > Cheers, > > Vince > > > > On Mon, Sep 8, 2008 at 4:27 AM, <[EMAIL PROTECTED]> wrote: > > > > > On 5 Sep, 18:33, Vinny Abello <[EMAIL PROTECTED]> wrote: > > > > I just upgraded from BIND 9.4.2 to BIND 9.4.2-P2-W1 on Windows > > Server > > > 2003. The service no longer crashes like it did in P1 and P2, however > > after > > > about 12 hours of load, named just stops responding to queries > > completely. > > > The service appears that it is still running but will not respond to > > any > > > type of query. I've restarted it and it came back to life again. I'm > > going > > > to watch it more carefully to look for any other types of symptoms. I > > > checked the log files and nothing out of the ordinary was in the > > logs. In > > > fact, according to the logs, it appears that zone transfers were > > still > > > happily taking place while it was not responding to queries. > > > > > > > [snip] > > > > > > > > Some possible information that might help with this server's > > > configuration. This server has multiple IPv4 IP addresses bound to > > the same > > > network and same NIC. There is no IPv6 stack installed on the server. > > This > > > server currently does recursion and also hosts some secondary zones > > as well. > > > > > > > > -Vinny > > > > > > Hi, > > > > > > Just want to add a 'me too'. We've got a very similar setup: Windows > > > 2003 SP2 with multiple IPv4 addresses bound to a single NIC. No IPv6. > > > Server is authoratitive for about 300 zones files and also recurses. > > > Just stops answering UDP queries after a few hours, it's OK if you > > > stop and restart it. No event logs worth mentioning. > > > > > > Darren > > > > > > > > > > > > > > >
