Quote:
Originally Posted by bathory
.
I see from named startup logs that your dns has ip 192.168.2.2, so if you have other computers in your network that use your dns, you must create a normal 2.168.192.in-addr.arpa zone file.
I don't see in bind startup logs, if the zones you have defined are loaded, but I guess the logging is done in another file defined in logging.conf
Note also that dig is working because your dns is configured as a caching dns only.
|
There is only the one computer connected to my DSL line. The reason I'm 'trying' to get named setup is to speedup queries when running my NANAS reporting script. Apparently logging is to syslog:
Mar 18 17:43:07 localhost named[10177]: starting BIND 9.5.0-P2 -u named -t /var/lib/named
Mar 18 17:43:08 localhost named[10177]: found 1 CPU, using 1 worker thread
Mar 18 17:43:08 localhost named[10177]: loading configuration from '/etc/named.conf'
Mar 18 17:43:08 localhost named[10177]: listening on IPv4 interface lo, 127.0.0.1#53
Mar 18 17:43:08 localhost named[10177]: listening on IPv4 interface eth1, 192.168.2.2#53
Mar 18 17:43:08 localhost named[10177]: default max-cache-size (33554432) applies
Mar 18 17:43:08 localhost named[10177]: automatic empty zone: 127.IN-ADDR.ARPA
Mar 18 17:43:08 localhost named[10177]: automatic empty zone: 254.169.IN-ADDR.ARPA
Mar 18 17:43:08 localhost named[10177]: automatic empty zone: 2.0.192.IN-ADDR.ARPA
Mar 18 17:43:08 localhost named[10177]: automatic empty zone: 255.255.255.255.IN-ADDR.ARPA
Mar 18 17:43:08 localhost named[10177]: automatic empty zone: 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
Mar 18 17:43:08 localhost named[10177]: automatic empty zone: 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
Mar 18 17:43:08 localhost named[10177]: automatic empty zone: D.F.IP6.ARPA
Mar 18 17:43:08 localhost named[10177]: automatic empty zone: 8.E.F.IP6.ARPA
Mar 18 17:43:08 localhost named[10177]: automatic empty zone: 9.E.F.IP6.ARPA
Mar 18 17:43:08 localhost named[10177]: automatic empty zone: A.E.F.IP6.ARPA
Mar 18 17:43:08 localhost named[10177]: automatic empty zone: B.E.F.IP6.ARPA
Mar 18 17:43:08 localhost named[10177]: default max-cache-size (33554432) applies: view _bind
Mar 18 17:43:08 localhost named[10177]: command channel listening on 127.0.0.1#953
The /var/lib/named/etc/logging.conf shows:
logging {
channel security_channel {
file "/var/log/security.log" versions 4 size 10m;
print-category yes;
print-severity yes;
print-time yes;
severity info;
};
channel default_channel {
file "/var/log/default.log" versions 4 size 10m;
print-category yes;
print-severity yes;
print-time yes;
};
channel xfer-in_channel {
file "/var/log/xfer-in.log" versions 4 size 10m;
severity info;
print-category yes;
print-severity yes;
print-time yes;
};
channel xfer-out_channel {
file "/var/log/xfer-out.log" versions 4 size 10m;
severity info;
print-category yes;
print-severity yes;
print-time yes;
};
channel update_channel {
file "/var/log/update.log" versions 4 size 10m;
severity info;
print-category yes;
print-severity yes;
print-time yes;
};
channel notify_channel {
file "/var/log/notify.log" versions 4 size 10m;
severity info;
print-category yes;
print-severity yes;
print-time yes;
};
channel "querylog" {
file "/var/log/query.log" versions 4 size 10m;
print-time yes;
};
category queries { querylog; };
category security { security_channel; };
category default { default_channel; };
category xfer-in { xfer-in_channel; };
category xfer-out { xfer-out_channel; };
category notify { notify_channel; };
category update { null; };
category lame-servers { null; };
category "delegation-only" { "null" ; };
};
Though they are actually in /var/lib/named/var/log
-rw-r--r-- 1 named named 155531 2009-03-18 17:43 default.log
-rw-r--r-- 1 named named 0 2009-03-13 20:36 notify.log
-rw-r--r-- 1 named named 2000742 2009-03-18 18:55 query.log
-rw-r--r-- 1 named named 129 2009-03-16 04:03 security.log
-rw-r--r-- 1 named named 0 2009-03-13 20:36 update.log
-rw-r--r-- 1 named named 0 2009-03-13 20:36 xfer-in.log
-rw-r--r-- 1 named named 0 2009-03-13 20:36 xfer-out.log
Though no matter where I put them the default.log shows that files are not found, example below:
18-Mar-2009 17:43:08.039 general: error: zone 0.in-addr.arpa/IN: loading from master file /var/lib/named/var/lib/named/reverse/named.zero failed: file not found
18-Mar-2009 17:43:08.040 general: error: zone 10.IN-ADDR.ARPA/IN: loading from master file /var/lib/named/var/lib/named/master/empty failed: file not found
I hope I sufficiently answered your question
Chris