LINUX.ORG.RU
решено ФорумAdmin

bind...

 , , ,


0

1

Bind и снова bind... Дома ковыряю по тихой bind master + slave Столкнулся с такой проблемой, что после настройки мастера и раба, зоны с мастера на раба ни в какую не гуляют. Вот что в логах на слейве:

[cut=лог слэйв]
21-Feb-2017 05:47:02.587 xfer-in: transfer of '168.192.in-addr.arpa/IN' from 192.168.1.100#53: failed to connect: host unreachable
21-Feb-2017 05:47:02.587 xfer-in: transfer of '168.192.in-addr.arpa/IN' from 192.168.1.100#53: Transfer completed: 0 messages, 0 records, 0 bytes, 0.001 secs (0 bytes/sec)
21-Feb-2017 05:47:03.086 general: zone hatsnal.ru/IN: refresh: retry limit for master 192.168.1.100#53 exceeded (source 0.0.0.0#0)
21-Feb-2017 05:48:06.991 general: received control channel command 'reload'
21-Feb-2017 05:48:06.991 general: loading configuration from '/etc/named.conf'
21-Feb-2017 05:48:06.992 general: using default UDP/IPv4 port range: [1024, 65535]
21-Feb-2017 05:48:06.992 general: using default UDP/IPv6 port range: [1024, 65535]
21-Feb-2017 05:48:06.993 general: sizing zone task pool based on 7 zones
21-Feb-2017 05:48:06.994 general: Warning: 'empty-zones-enable/disable-empty-zone' not set: disabling RFC 1918 empty zones
21-Feb-2017 05:48:06.995 general: reloading configuration succeeded
21-Feb-2017 05:48:06.996 general: reloading zones succeeded
21-Feb-2017 05:49:36.999 general: zone 168.192.in-addr.arpa/IN: refresh: retry limit for master 192.168.1.100#53 exceeded (source 0.0.0.0#0)
21-Feb-2017 05:49:37.500 general: zone hatsnal.ru/IN: refresh: retry limit for master 192.168.1.100#53 exceeded (source 0.0.0.0#0)

На мастере:

21-Feb-2017 05:47:02.587 xfer-in: transfer of '168.192.in-addr.arpa/IN' from 192.168.1.100#53: failed to connect: host unreachable
21-Feb-2017 05:47:02.587 xfer-in: transfer of '168.192.in-addr.arpa/IN' from 192.168.1.100#53: Transfer completed: 0 messages, 0 records, 0 bytes, 0.001 secs (0 bytes/sec)
21-Feb-2017 05:47:03.086 general: zone hatsnal.ru/IN: refresh: retry limit for master 192.168.1.100#53 exceeded (source 0.0.0.0#0)
21-Feb-2017 05:48:06.991 general: received control channel command 'reload'
21-Feb-2017 05:48:06.991 general: loading configuration from '/etc/named.conf'
21-Feb-2017 05:48:06.992 general: using default UDP/IPv4 port range: [1024, 65535]
21-Feb-2017 05:48:06.992 general: using default UDP/IPv6 port range: [1024, 65535]
21-Feb-2017 05:48:06.993 general: sizing zone task pool based on 7 zones
21-Feb-2017 05:48:06.994 general: Warning: 'empty-zones-enable/disable-empty-zone' not set: disabling RFC 1918 empty zones
21-Feb-2017 05:48:06.995 general: reloading configuration succeeded
21-Feb-2017 05:48:06.996 general: reloading zones succeeded
21-Feb-2017 05:49:36.999 general: zone 168.192.in-addr.arpa/IN: refresh: retry limit for master 192.168.1.100#53 exceeded (source 0.0.0.0#0)
21-Feb-2017 05:49:37.500 general: zone hatsnal.ru/IN: refresh: retry limit for master 192.168.1.100#53 exceeded (source 0.0.0.0#0)

Конфиг мастера:

options
{
                directory "/var/named";
                dump-file               "data/cache_dump.db";
                statistics-file         "data/named_stats.txt";
                memstatistics-file      "data/named_mem_stats.txt";
                version "Made in USSR";
                listen-on {localhost; 192.168.1.100; };
                allow-transfer {192.168.1.101; };
                allow-query {trusted-networks; };
                allow-recursion {trusted-networks; };
                forwarders {192.168.1.1; };
};
logging
{
                channel default_ch {
                        file "data/named-base.log";
                        severity info;
                        print-time yes;
                        print-category yes;
                };

                channel security_ch {
                        file "data/named-security.log";
                        severity info;
                        print-time yes;
                        print-category yes;
                };
category default { default_ch; };
category security { security_ch; };

};

acl "trusted-networks" {localhost; 192.168.1.0/24; };

zone "hatsnal.ru" IN {
        type master;
        file "hatsnal.ru";
};

zone "168.192.in-addr.arpa" {
        type master;
        file "168.192.rev";
};

include "/etc/named.rfc1912.zones";

Конфиг слэйва:

options
{
                directory "/var/named";
                dump-file               "data/cache_dump.db";
                statistics-file         "data/named_stats.txt";
                memstatistics-file      "data/named_mem_stats.txt";
                version "Made in USSR";
                listen-on {localhost; 192.168.1.101; };
                allow-transfer {none; };
                allow-query {trusted-networks; };
                allow-recursion {trusted-networks; };
                forwarders {192.168.1.100; };
};
logging
{
                channel default_ch {
                        file "data/named-base.log";
                        severity info;
                        print-time yes;
                        print-category yes;
                };

                channel security_ch {
                        file "data/named-security.log";
                        severity info;
                        print-time yes;
                        print-category yes;
                };
category default { default_ch; };
category security { security_ch; };

};

acl "trusted-networks" {localhost; 192.168.1.0/24; };

zone "hatsnal.ru" IN {
        type slave;
        file "slaves/hatsnal.ru";
        masters {192.168.1.100; };
};

zone "168.192.in-addr.arpa" {
        type slave;
        file "slaves/168.192.rev";
        masters {192.168.1.100; };
};

include "/etc/named.rfc1912.zones";

Вы разницу между конфигами видите? Я вот «наискосок» нифига не вижу.
ЗЫ и логи в [ code] завернуть не лишне было бы

anc ★★★★★ ()
Последнее исправление: anc (всего исправлений: 1)
Ответ на: комментарий от hatsnal

Дабл копи сделал, исправил.

С логами похоже также.
Но не суть xfer-in: transfer of '168.192.in-addr.arpa/IN' from 192.168.1.100#53: failed to connect: host unreachable Какбэ намекает

anc ★★★★★ ()
Ответ на: комментарий от hatsnal

Отметьте как решенную, а то народ может два одинаковых лога начать курить потом.

anc ★★★★★ ()
Вы не можете добавлять комментарии в эту тему. Тема перемещена в архив.