URL: https://www.opennet.me/cgi-bin/openforum/vsluhboard.cgi
Форум: vsluhforumID1
Нить номер: 92435
[ Назад ]

Исходное сообщение
"bind dns"
Отправлено roofut , 13-Окт-11 11:42

Есть днс сервер и 3000 пользователей обращаюшихся к нему. На серваке 4 гига рама. Ресурсов вроде бы хватает, но периодически ответ от сервера не идет , адреса не резольвятся. стоит bind на suse. Появилось желание поставить другой сервер. есть ли лучшая альтернатива на линуксе, либо другое решение для провайдеров ?

Содержание

bind dns,andy03, 22:07 , 13-Окт-11
- bind dns,roofut, 10:02 , 18-Окт-11
bind dns,Pahanivo, 07:46 , 14-Окт-11
- bind dns,roofut, 10:04 , 18-Окт-11
  - bind dns,Pahanivo, 10:36 , 18-Окт-11

Сообщения в этом обсуждении

"bind dns"
Отправлено andy03 , 13-Окт-11 22:07

> Есть днс сервер и 3000 пользователей обращаюшихся к нему. На серваке 4
> гига рама. Ресурсов вроде бы хватает, но периодически ответ от сервера
> не идет , адреса не резольвятся. стоит bind на suse. Появилось
> желание поставить другой сервер. есть ли лучшая альтернатива на линуксе, либо
> другое решение для провайдеров ?
в логах службы/сервера что?
перезапуск службы спасает?

"bind dns"
Отправлено roofut , 18-Окт-11 10:02

>> Есть днс сервер и 3000 пользователей обращаюшихся к нему. На серваке 4
>> гига рама. Ресурсов вроде бы хватает, но периодически ответ от сервера
>> не идет , адреса не резольвятся. стоит bind на suse. Появилось
>> желание поставить другой сервер. есть ли лучшая альтернатива на линуксе, либо
>> другое решение для провайдеров ?
> в логах службы/сервера что?
> перезапуск службы спасает?
да спасает, вот логи

ct 13 14:22:47 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 1.0.168.192.in-addr.arpa
Oct 13 14:22:47 billing named[7413]: client 95.86.129.34#49626: RFC 1918 response from Internet for 61.1.168.192.in-addr.arpa
Oct 13 14:22:47 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 1.0.168.192.in-addr.arpa
Oct 13 14:22:48 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 1.0.168.192.in-addr.arpa
Oct 13 14:22:48 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 143.0.168.192.in-addr.arpa
Oct 13 14:22:48 billing named[7413]: client 95.86.129.34#49626: RFC 1918 response from Internet for 56.1.168.192.in-addr.arpa
Oct 13 14:22:48 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 1.0.168.192.in-addr.arpa
Oct 13 14:22:48 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 1.0.168.192.in-addr.arpa
Oct 13 14:22:48 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 1.0.168.192.in-addr.arpa
Oct 13 14:22:48 billing named[7413]: client 95.86.129.34#49626: RFC 1918 response from Internet for 56.1.168.192.in-addr.arpa
Oct 13 14:22:48 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 1.0.168.192.in-addr.arpa
Oct 13 14:22:48 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 1.0.168.192.in-addr.arpa
Oct 13 14:22:48 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 11.0.168.192.in-addr.arpa
Oct 13 14:22:48 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 223.0.168.192.in-addr.arpa
Oct 13 14:22:48 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 1.0.168.192.in-addr.arpa
Oct 13 14:22:48 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 1.0.168.192.in-addr.arpa
Oct 13 14:22:48 billing named[7413]: client 95.86.129.34#49626: RFC 1918 response from Internet for 17.1.168.192.in-addr.arpa
Oct 13 14:22:48 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 1.0.168.192.in-addr.arpa
Oct 13 14:22:48 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 11.0.168.192.in-addr.arpa
Oct 13 14:22:48 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 1.0.168.192.in-addr.arpa
Oct 13 14:22:48 billing named[7413]: too many timeouts resolving 'Abiulk7JbAQ-BLoZJMYUH4F-Bkj6leAQABAgAAEQAA.a.immunet.com/TXT' (in 'a.immunet.com'?): disabling EDNS
Oct 13 14:22:48 billing named[7413]: client 95.86.129.34#49626: RFC 1918 response from Internet for 17.1.168.192.in-addr.arpa
Oct 13 14:22:48 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 30.0.168.192.in-addr.arpa
Oct 13 14:22:48 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 1.0.168.192.in-addr.arpa
Oct 13 14:22:48 billing named[7413]: client 95.86.129.34#49626: RFC 1918 response from Internet for 17.1.168.192.in-addr.arpa
Oct 13 14:22:48 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 1.0.168.192.in-addr.arpa
Oct 13 14:22:48 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 143.0.168.192.in-addr.arpa
Oct 13 14:22:48 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 143.0.168.192.in-addr.arpa
Oct 13 14:22:48 billing named[7413]: client 95.86.129.34#49626: RFC 1918 response from Internet for 61.1.168.192.in-addr.arpa
Oct 13 14:22:48 billing named[7413]: client 95.86.129.34#49626: RFC 1918 response from Internet for 61.1.168.192.in-addr.arpa
Oct 13 14:22:48 billing named[7413]: client 95.86.129.34#49626: RFC 1918 response from Internet for 17.1.168.192.in-addr.arpa
Oct 13 14:22:48 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 1.0.168.192.in-addr.arpa
Oct 13 14:22:48 billing named[7413]: client 95.86.129.34#49626: RFC 1918 response from Internet for 102.1.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.34#49626: RFC 1918 response from Internet for 17.1.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 1.0.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: too many timeouts resolving 'ns1.lgdacom.net/A' (in 'lgdacom.net'?): disabling EDNS
Oct 13 14:22:49 billing named[7413]: too many timeouts resolving 'ns3.lgdacom.net/AAAA' (in 'lgdacom.net'?): disabling EDNS
Oct 13 14:22:49 billing named[7413]: unexpected RCODE (REFUSED) resolving 'tep.xylocomods.com/A/IN': 67.208.74.19#53
Oct 13 14:22:49 billing named[7413]: client 95.86.129.34#49626: RFC 1918 response from Internet for 17.1.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.34#49626: RFC 1918 response from Internet for 17.1.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.34#49626: RFC 1918 response from Internet for 101.1.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 11.0.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 11.0.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 11.0.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 11.0.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 1.0.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 1.0.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 34.0.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 11.0.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 18.0.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 34.0.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 18.0.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 18.0.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 18.0.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.34#49626: RFC 1918 response from Internet for 102.1.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 18.0.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.34#49626: RFC 1918 response from Internet for 75.1.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 1.0.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: unexpected RCODE (REFUSED) resolving 'tep.xylocomods.com/A/IN': 69.93.94.154#53
Oct 13 14:22:49 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 18.0.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 11.0.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.34#49626: RFC 1918 response from Internet for 55.1.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 11.0.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.34#49626: RFC 1918 response from Internet for 55.1.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.34#49626: RFC 1918 response from Internet for 55.1.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.34#49626: RFC 1918 response from Internet for 55.1.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.34#49626: RFC 1918 response from Internet for 55.1.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 11.0.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 11.0.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 1.0.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.34#49626: RFC 1918 response from Internet for 55.1.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 11.0.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.34#49626: RFC 1918 response from Internet for 55.1.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 11.0.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.34#49626: RFC 1918 response from Internet for 55.1.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.34#49626: RFC 1918 response from Internet for 55.1.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 1.0.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: unexpected RCODE (REFUSED) resolving 'tep.xylocomods.com/A/IN': 67.208.84.25#53
Oct 13 14:22:49 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 1.0.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.34#49626: RFC 1918 response from Internet for 102.1.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.34#49626: RFC 1918 response from Internet for 55.1.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.34#49626: RFC 1918 response from Internet for 55.1.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.34#49626: RFC 1918 response from Internet for 102.1.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.34#49626: RFC 1918 response from Internet for 55.1.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 1.0.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 1.0.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.34#49626: RFC 1918 response from Internet for 56.1.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.34#49626: RFC 1918 response from Internet for 56.1.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.34#49626: RFC 1918 response from Internet for 55.1.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 1.0.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 11.0.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 72.0.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 11.0.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.34#49626: RFC 1918 response from Internet for 102.1.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 11.0.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.34#49626: RFC 1918 response from Internet for 55.1.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 1.0.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 11.0.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 18.0.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 18.0.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 1.0.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: unexpected RCODE (REFUSED) resolving 'tep.xylocomods.com/A/IN': 69.26.176.28#53
Oct 13 14:22:49 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 18.0.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.34#49626: RFC 1918 response from Internet for 55.1.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 1.0.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 1.0.168.192.in-addr.arpa
Oct 13 14:22:49 billing named[7413]: client 95.86.129.34#49626: RFC 1918 response from Internet for 55.1.168.192.in-addr.arpa
Oct 13 14:22:50 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 143.0.168.192.in-addr.arpa
Oct 13 14:22:50 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 1.0.168.192.in-addr.arpa
Oct 13 14:22:50 billing named[7413]: client 95.86.148.122#29478: RFC 1918 response from Internet for 100.1.168.192.in-addr.arpa
Oct 13 14:22:50 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet for 1.0.168.192.in-addr.arpa
Oct 13 14:22:50 billing named[7413]: client 95.86.129.34#49626: RFC 1918 response from Internet for 55.1.168.192.in-addr.arpa

"bind dns"
Отправлено Pahanivo , 14-Окт-11 07:46

> Есть днс сервер и 3000 пользователей обращаюшихся к нему. На серваке 4
> гига рама. Ресурсов вроде бы хватает, но периодически ответ от сервера
> не идет , адреса не резольвятся. стоит bind на suse. Появилось
> желание поставить другой сервер. есть ли лучшая альтернатива на линуксе, либо
> другое решение для провайдеров ?
конфиги в студию
rndc status в моменты "тупизма"

"bind dns"
Отправлено roofut , 18-Окт-11 10:04

>> Есть днс сервер и 3000 пользователей обращаюшихся к нему. На серваке 4
>> гига рама. Ресурсов вроде бы хватает, но периодически ответ от сервера
>> не идет , адреса не резольвятся. стоит bind на suse. Появилось
>> желание поставить другой сервер. есть ли лучшая альтернатива на линуксе, либо
>> другое решение для провайдеров ?
> конфиги в студию
> rndc status в моменты "тупизма"
options {
# The directory statement defines the name server's working directory
directory "/var/lib/named";
# Write dump and statistics file to the log subdirectory. The
# pathenames are relative to the chroot jail.
dump-file "/var/log/named_dump.db";
statistics-file "/var/log/named.stats";
# The forwarders record contains a list of servers to which queries
# should be forwarded. Enable this line and modify the IP address to
# your provider's name server. Up to three servers may be listed.
#forwarders { 192.0.2.1; 192.0.2.2; };
# Enable the next entry to prefer usage of the name server declared in
# the forwarders section.
#forward first;
# The listen-on record contains a list of local network interfaces to
# listen on. Optionally the port can be specified. Default is to
# listen on all interfaces found on your system. The default port is
# 53.
#listen-on port 53 { 127.0.0.1; };
# The listen-on-v6 record enables or disables listening on IPv6
# interfaces. Allowed values are 'any' and 'none' or a list of
# addresses.
listen-on-v6 { any; };
# The next three statements may be needed if a firewall stands between
# the local server and the internet.
#query-source address * port 53;
#transfer-source * port 53;
#notify-source * port 53;
# The allow-query record contains a list of networks or IP addresses
# to accept and deny queries from. The default is to allow queries
# from all hosts.
allow-query { any; };
# If notify is set to yes (default), notify messages are sent to other
# name servers when the the zone data is changed. Instead of setting
# a global 'notify' statement in the 'options' section, a separate
# 'notify' can be added to each zone definition.
notify no;
};
# To configure named's logging remove the leading '#' characters of the
# following examples.
#logging {
# # Log queries to a file limited to a size of 100 MB.
# channel query_logging {
# file "/var/log/named_querylog"
# versions 3 size 100M;
# print-time yes; // timestamp log entries
# };
# category queries {
# query_logging;
# };
#
# # Or log this kind alternatively to syslog.
# channel syslog_queries {
# syslog user;
# severity info;
# };
# category queries { syslog_queries; };
#
# # Log general name server errors to syslog.
# channel syslog_errors {
# syslog user;
# severity error;
# };
# category default { syslog_errors; };
#
# # Don't log lame server messages.
# category lame-servers { null; };
#};
# The following zone definitions don't need any modification. The first one
# is the definition of the root name servers. The second one defines
# localhost while the third defines the reverse lookup for localhost.
zone "." in {
type hint;

zone "localhost" in {
type master;
file "localhost.zone";
};
zone "0.0.127.in-addr.arpa" in {
type master;
file "127.0.0.zone";
};
...
Далее идут мастер зоны клиентов

rndc status где смотреть ?

"bind dns"
Отправлено Pahanivo , 18-Окт-11 10:36

> #listen-on port 53 { 127.0.0.1; };
> listen-on-v6 { any; };
ы?
> for 11.0.168.192.in-addr.arpa
> Oct 13 14:22:48 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet
> for 223.0.168.192.in-addr.arpa
> Oct 13 14:22:48 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet
> for 1.0.168.192.in-addr.arpa
> Oct 13 14:22:48 billing named[7413]: client 95.86.129.2#1682: RFC 1918 response from Internet
> for 1.0.168.192.in-addr.arpa
> Oct 13 14:22:48 billing named[7413]: client 95.86.129.34#49626: RFC 1918 response from
> Internet for 17.1.168.192.in-addr.arpa
о?