Actually to add to the dns issue. What I found most interesting is that I ran bind so I could watch anything it would log, once it started and said it was sending its nodify it just sits and I never see any logging beyond that point. Here is a sample. Starting domain name service: namedOct 14 10:40:04.119 starting BIND 9.2.1 -g Oct 14 10:40:04.125 using 1 CPU Oct 14 10:40:04.174 loading configuration from '/etc/bind/named.conf' Oct 14 10:40:04.261 no IPv6 interfaces found Oct 14 10:40:04.262 listening on IPv4 interface lo, 127.0.0.1#53 Oct 14 10:40:04.269 listening on IPv4 interface eth0, 192.168.1.11#53 Oct 14 10:40:04.296 command channel listening on 127.0.0.1#953 Oct 14 10:40:04.297 ignoring config file logging statement due to -g option Oct 14 10:40:04.310 zone 0.0.127.in-addr.arpa/IN: loaded serial 2000121701 Oct 14 10:40:04.324 zone lrxms.net/IN: loaded serial 2002101301 Oct 14 10:40:04.325 running Oct 14 10:40:04.329 zone lrxms.net/IN: sending notifies (serial 2002101301) ./bind9: line 38: 730 Quit start-stop-daemon --start --quiet --pidfile /var/run/named.pid --exec /usr/sbin/named -- $OPTS . Now this is all you see even while making querries on another console it never changes. I suspect and will have to do some real digging, but Debian does not have bind compile or configured to log the same as bind does on my Slackware box. If anyone is using Debian and bind and could tell me how its logging I'd appreciate it. I found a file called named.run and it had some info in it, but wasn't current. I tried moving it and touching a new file, but it was never populated. I then tried using the tail command to see if anything was being logged and nothing. This is really annoying. I guess I'm going to have to do more rtfming here because this doesn't make much sense and is proving a bit more tricky to find things. I guess I could just get my own bind package and compile from scratch and know exactly where things are and doing what. tnx
