Добрыня!
Имеется CentOS 6.4 x32, установлен пакет Bind. Настроен кэширующий DNS сервер.
Теперь о проблеме, в логах сыплются ошибки, лог файл /var/named/data/named.run
растет быстро вот с такими error'ами:
unexpected RCODE REFUSED
error (unexpected RCODE REFUSED) resolving '229.243.72.202.in-addr.arpa/PTR/IN': 202.72.241.5#53
error (unexpected RCODE REFUSED) resolving '229.243.72.202.in-addr.arpa/PTR/IN': 202.72.241.4#53
error (unexpected RCODE REFUSED) resolving '203.55.68.118.in-addr.arpa/PTR/IN': 210.245.31.10#53
error (unexpected RCODE REFUSED) resolving '229.243.72.202.in-addr.arpa/PTR/IN': 202.72.241.4#53
error (unexpected RCODE REFUSED) resolving '229.243.72.202.in-addr.arpa/PTR/IN': 202.72.241.5#53unexpected RCODE SERVFAIL
error (unexpected RCODE SERVFAIL) resolving '218.152.251.87.in-addr.arpa/PTR/IN': 81.91.177.130#53
error (unexpected RCODE SERVFAIL) resolving '218.152.251.87.in-addr.arpa/PTR/IN': 81.91.176.2#53
error (unexpected RCODE SERVFAIL) resolving '218.152.251.87.in-addr.arpa/PTR/IN': 81.91.176.2#53
error (unexpected RCODE SERVFAIL) resolving '218.152.251.87.in-addr.arpa/PTR/IN': 81.91.177.130#53Конфиг /etc/named.conf:
//
// named.conf
//
// Provided by Red Hat bind package to configure the ISC BIND named(8) DNS
// server as a caching only nameserver (as a localhost DNS resolver only).
//
// See /usr/share/doc/bind*/sample/ for example named configuration files.
//
options {
listen-on port 53 { localhost; 127.0.0.1; 192.168.1.2; };
#listen-on-v6 port 53 { ::1; };
listen-on-v6 port 53 { none; };
forwarders {8.8.8.8;8.8.4.4;};
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";
allow-query { localhost; 127.0.0.1; 192.168.1.0/24;};
allow-recursion {127.0.0.1;192.168.1.0/24;};
dnssec-enable no;
dnssec-validation no;
dnssec-lookaside auto;
/* Path to ISC DLV key */
bindkeys-file "/etc/named.iscdlv.key";
managed-keys-directory "/var/named/dynamic";
};
logging {
channel default_debug {
file "data/named.run";
severity dynamic;
};
};
zone "." IN {
type hint;
file "named.ca";
};
include "/etc/named.rfc1912.zones";
include "/etc/named.root.key";Конфиг /etc/resolv.conf
nameserver 127.0.0.1Как правильно настроить чтобы логи не росли.
Спасибо
_
UP
Вообще советуют вырубать логирование именно по этой теме (что я и сделал только что), это делается добавлением строчки в секцию logging {}, файла named.conf.
logging {
category lame-servers { null; };Вот что пишут HP:
Comparing the source code of BIND 9.3.2 with BIND 9.2.0 reveals that these 'unexpected RCODE' messages are logged under category lame-servers and that the logging in this category has been significantly enhanced so that when problems arise with resolution where the nameserver has to refer to another nameserver, more detailed information is now logged. NOTE, this is not necessarily forwarding - it can be regular recursive query handling where the nameserver goes to another to find the answer.
The reasoning behind this enhanced logging is that the DNS administrator can see more clearly from the log messages which nameservers have a problem and what that problem is, and can then inform the owners (by looking up the SOA of the domain using DIG) so that it can be fixed. As a result, BIND 9.3.2 has some new lameserver scenarios which are being reported which were not explicitly seen before.
