Set bind to listen to IP, not network, for example 10.10.80.1, no
10.10.80.0
Miguel A. Velasco wrote / napísal(a):
Hello all,
I´ve installed a proxy Squid in my gateway and a Cache DNS Server with
bind. The problem is the server is only resolving is own querys but not
the client queries from my company.
When I do:
$service named start
I see in /var/log/messages:
starting BIND 9.3.4-P1 -u named -t /var/named/chroot
found 1 CPU, using 1 worker thread
loading configuration from '/etc/named.conf'
listening on IPv6 interface lo, ::1#53
listening on IPv4 interface lo, 127.0.0.1#53
command channel listening on 127.0.0.1#953
command channel listening on ::1#953
zone 0.in-addr.arpa/IN/localhost_resolver: loaded serial 42
zone 0.0.127.in-addr.arpa/IN/localhost_resolver: loaded serial 1997022700
zone 255.in-addr.arpa/IN/localhost_resolver: loaded serial 42
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.ip6.arpa/IN/localhost_resolver:
loaded serial 1997022700
zone localdomain/IN/localhost_resolver: loaded serial 42
zone localhost/IN/localhost_resolver: loaded serial 42
running
I don´t understand why is only "listening on IPv4 interface lo,
127.0.0.1#53"
I have bind-chroot installed with the following options in
/etc/named.conf:
options {
listen-on port 53 { 127.0.0.1; 10.10.80.0; };
listen-on-v6 port 53 { ::1; };
directory "/var/named";
dump-file "/var/named/data/cache_dump.db";
statistics-file "/var/named/data/named_stats.txt";
memstatistics-file "/var/named/data/named_mem_stats.txt";
// Those options should be used carefully because they disable
port
// randomization
// query-source port 53;
// query-source-v6 port 53;
allow-query { localhost; };
};
logging {
channel default_debug {
file "data/named.run";
severity dynamic;
};
};
view localhost_resolver {
match-clients { localhost; };
match-destinations { localhost; };
recursion yes;
include "/etc/named.rfc1912.zones";
};
Where 10.10.80.0 is my network range. What may I do my server really
listen for all my network? Nowadays it´s listenning just itself ....
Thanks very much for your attention.
Miguel A. Velasco
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
