hi,
i've got a problem (like in title) with bind9, bind service is working correctly inside my local net, (what is strange) only between units (like my laptop -> server), unfortunately not between my router -> server (which is wrt-54g with tomato) the same with units from outside. port forwarding is set correctly. everything was working till yesterday. i have no idea why - i've made no changes in my confs. a month ago i had the same problem, but solved by commenting query-source in named.conf. my dns is working as a master, secondery is at freedns.sgh.waw.pl. pf is configured properly, i also tried with pf turned off - with no changes.
all other daemons are responsing :80 :22 :21 :110 etc. only dns not :|
i've got a problem (like in title) with bind9, bind service is working correctly inside my local net, (what is strange) only between units (like my laptop -> server), unfortunately not between my router -> server (which is wrt-54g with tomato) the same with units from outside. port forwarding is set correctly. everything was working till yesterday. i have no idea why - i've made no changes in my confs. a month ago i had the same problem, but solved by commenting query-source in named.conf. my dns is working as a master, secondery is at freedns.sgh.waw.pl. pf is configured properly, i also tried with pf turned off - with no changes.
Code:
### named.conf
options {
// Relative to the chroot directory, if any
directory "/etc/namedb";
pid-file "/var/run/named/pid";
dump-file "/var/dump/named_dump.db";
statistics-file "/var/stats/named.stats";
listen-on { global-ip; 127.0.0.1; 10.0.0.2; };
//query-source address 10.0.0.2 port 53;
recursion no;
version "go away";
};
zone "0.0.127.in-addr.arpa" {
type master;
file "127.0.0";
};
zone "domain.org" {
type master;
file "domain.org";
allow-transfer {
193.111.27.194; 194.145.96.21;
};
};
key "rndc-key" {
algorithm hmac-md5;
secret "************************************";
};
controls {
inet * allow { 127.0.0.1; } keys { "rndc-key"; };
};
### netstat
tcp4 0 0 *.953 *.* LISTEN
tcp4 0 0 127.0.0.1.53 *.* LISTEN
tcp4 0 0 10.0.0.2.53 *.* LISTEN
### named -4 -g
10-Sep-2009 11:45:54.539 starting BIND 9.3.6-P1 -4 -g
10-Sep-2009 11:45:54.539 using up to 4096 sockets
10-Sep-2009 11:45:54.575 loading configuration from '/usr/local/etc/named.conf'
10-Sep-2009 11:45:54.600 using default UDP/IPv4 port range: [49152, 65535]
10-Sep-2009 11:45:54.600 using default UDP/IPv6 port range: [49152, 65535]
10-Sep-2009 11:45:54.602 no IPv6 interfaces found
10-Sep-2009 11:45:54.602 listening on IPv4 interface rl0, 10.0.0.2#53
10-Sep-2009 11:45:54.603 listening on IPv4 interface lo0, 127.0.0.1#53
10-Sep-2009 11:45:54.638 command channel listening on 0.0.0.0#953
10-Sep-2009 11:45:54.639 ignoring config file logging statement due to -g option
[loading outside zones .arpa]
10-Sep-2009 11:45:54.732 zone ip6.int/IN: loaded serial 42
10-Sep-2009 11:45:54.733 zone localhost/IN: loaded serial 42
10-Sep-2009 11:45:54.740 zone domena.org/IN: loaded serial 1224794394
10-Sep-2009 11:45:54.751 running
10-Sep-2009 11:45:54.772 zone domena.org/IN: sending notifies (serial 1224794394)
### /var/log/messages
Sep 10 11:53:34 host named[8669]: starting BIND 9.3.6-P1 -t /var/named -u bind
Sep 10 11:53:34 host named[8669]: command channel listening on 0.0.0.0#953
Sep 10 11:53:34 host named[8669]: the working directory is not writable
