Re: named listening on LAN

2007-07-11 Thread Zbigniew Szalbot
Hello, This is interesting. I tried adding this to named.conf (adapted from man named.conf) /* logging { channel namedlog { file /var/log/named/nlog; severity info; print-time yes;

Re: named listening on LAN

2007-07-11 Thread Zbigniew Szalbot
Hello, On Wed, 11 Jul 2007 14:09:30 +0300, CK [EMAIL PROTECTED] wrote: Zbigniew Szalbot wrote: Now bind does not die but but it cannot find the log file: logging channel 'simple_log' file '/var/log/named/nlog': file not found ls /var/log/named/* /var/log/named/nlog Why would named not be

Re: named listening on LAN

2007-07-11 Thread Duane Hill
On Wed, 11 Jul 2007 at 13:16 +0200, [EMAIL PROTECTED] confabulated: Hello, On Wed, 11 Jul 2007 14:09:30 +0300, CK [EMAIL PROTECTED] wrote: Zbigniew Szalbot wrote: Now bind does not die but but it cannot find the log file: logging channel 'simple_log' file '/var/log/named/nlog': file not

Re: named listening on LAN

2007-07-11 Thread Zbigniew Szalbot
Hello again, Jul 11 13:06:03 szalbot named[3319]: logging channel 'simple_log' file '/var/named/var/log/nlog': file not found Jul 11 13:06:03 szalbot named[3319]: isc_log_open '/var/named/var/log/nlog' failed: file not found I have it working with this: logging { channel

named listening on LAN

2007-07-11 Thread CK
Zbigniew Szalbot wrote: Now bind does not die but but it cannot find the log file: logging channel 'simple_log' file '/var/log/named/nlog': file not found ls /var/log/named/* /var/log/named/nlog Why would named not be able to find the log when it is there? The nlog file is owned by user bind

named listening on LAN

2007-07-10 Thread Zbigniew Szalbot
Hello, I am slowly trying various features of FBSD and I have just enabled named to be my local caching DNS server. It works fine but I have one question. I would like it to be a caching DNS server for my LAN. So following the Handbook I tried setting a proper LAN IP address of the named

Re: named listening on LAN

2007-07-10 Thread jbarnet
this is what I got: listen-on { 127.0.0.1; 192.168.11.50; }; Try that, restart and see if it works locally (from the server). Also the logs spit anything out? Other thing is firewall, I think simple blocks it by default? So you might want to try that. Zbigniew Szalbot wrote: