歡迎您光臨本站 註冊首頁

在DNS從伺服器無法同步主伺服器

←手機掃碼閱讀     火星人 @ 2014-03-04 , reply:0

在DNS從伺服器無法同步主伺服器

主DNS伺服器能夠正常的工作;
/var/log/messages 里記錄
... transfer of "dimain.com/IN" from 192.168.2.200#53 : failed while receving  responses :  file not found


主伺服器name.conf
//
// named.conf for Red Hat caching-nameserver
//

options {
    directory "/var/named";
    dump-file "/var/named/data/cache_dump.db";
        statistics-file "/var/named/data/named_stats.txt";
    /*
     * If there is a firewall between you and nameservers you want
     * to talk to, you might need to uncomment the query-source
     * directive below.  Previous versions of BIND always asked
     * questions using port 53, but BIND 8.1 uses an unprivileged
     * port by default.
     */
     // query-source address * port 53;
};

//
// a caching only nameserver config
//
controls {
    inet 127.0.0.1 allow { localhost; } keys { rndckey; };
};

view "2.0" {
match-clients { 192.168.2.0/24;};

zone "." IN {
    type hint;
    file "named.ca";
    };

zone "domain.com" IN {
    type master;
    file "2.0/named.hosts";
    allow-transfer { 192.168.2.201; };
    };

zone "168.192.in-addr.arpa" IN {
    type master;
    file "2.0/named.rev";
    allow-transfer { 192.168.2.201; };
    };

zone "localhost" IN {
    type master;
    file "localhost.zone";
    allow-update { none; };
    };

zone "0.0.127.in-addr.arpa" IN {
    type master;
    file "named.local";
    allow-update { none; };
    };
};

view "3.0" {
match-clients {192.168.3.0/24 ;};

zone "." IN {
    type hint;
    file "named.ca";
    };

zone "domain.com" IN {
    type master;
    file "3.0/named.hosts";
    allow-transfer { 192.168.2.201; };
    };

zone "168.192.in-addr.arpa" IN {
    type master;
    file "3.0/named.rev";
    allow-transfer { 192.168.2.201; };
    };

zone "localhost" IN {
    type master;
    file "localhost.zone";
    allow-update { none; };
    };

zone "0.0.127.in-addr.arpa" IN {
    type master;
    file "named.local";
    allow-update { none; };
    };
};

include "/etc/rndc.key";


從伺服器name。conf
//
// named.conf for Red Hat caching-nameserver
//

options {
    directory "/var/named";
    dump-file "/var/named/data/cache_dump.db";
        statistics-file "/var/named/data/named_stats.txt";
    /*
     * If there is a firewall between you and nameservers you want
     * to talk to, you might need to uncomment the query-source
     * directive below.  Previous versions of BIND always asked
     * questions using port 53, but BIND 8.1 uses an unprivileged
     * port by default.
     */
     // query-source address * port 53;
};

//
// a caching only nameserver config
//
controls {
    inet 127.0.0.1 allow { localhost; } keys { rndckey; };
};

view "2.0" {
match-clients { 192.168.2.0/24;};

zone "." IN {
    type hint;
    file "named.ca";
    };

zone "domain.com" IN {
    type slave;
    file "slaves/2.0/named.hosts";
    masters { 192.168.2.200; };
    };

zone "168.192.in-addr.arpa" IN {
    type slave;
    file "slaves/2.0/named.rev";
    masters { 192.168.2.200; };
    };

zone "localhost" IN {
    type master;
    file "localhost.zone";
    allow-update { none; };
    };

zone "0.0.127.in-addr.arpa" IN {
    type master;
    file "named.local";
    allow-update { none; };
    };
};

view "3.0" {
match-clients {192.168.3.0/24 ;};

zone "." IN {
    type hint;
    file "named.ca";
    };

zone "domain.com" IN {
    type slave;
    file "slaves/3.0/named.hosts";
    masters { 192.168.2.200; };
    };

zone "168.192.in-addr.arpa" IN {
    type slave;
    file "slaves/3.0/named.rev";
    masters { 192.168.2.200; };
    };

zone "localhost" IN {
    type master;
    file "localhost.zone";
    allow-update { none; };
    };

zone "0.0.127.in-addr.arpa" IN {
    type master;
    file "named.local";
    allow-update { none; };
    };
};

include "/etc/rndc.key";
《解決方案》

是不是我從伺服器的name.conf有錯,希望大蝦幫忙看下謝謝 了
《解決方案》

tree /var/named 的結果如何?
《解決方案》

log
主要出錯信息
Jul  6 01:42:55 second named: received notify for zone 'domain.com'
Jul  6 01:42:55 second named: received notify for zone 'domain.com'
Jul  6 01:42:55 second named: dumping master file: slaves/2.0/tmp-XXXXKW2X 8L: open: file not found
Jul  6 01:42:55 second named: transfer of 'domain.com/IN' from 192.168.2.2 00#53: failed while receiving responses: file not found
Jul  6 01:42:55 second named: transfer of 'domain.com/IN' from 192.168.2.2 00#53: end of transfer
Jul  6 01:42:55 second named: dumping master file: slaves/2.0/tmp-XXXXDPZP 61: open: file not found
Jul  6 01:42:55 second named: transfer of '168.192.in-addr.arpa/IN' from 1 92.168.2.200#53: failed while receiving responses: file not found
Jul  6 01:42:55 second named: transfer of '168.192.in-addr.arpa/IN' from 1 92.168.2.200#53: end of transfer
Jul  6 01:43:31 second named: dumping master file: slaves/3.0/tmp-XXXXomFj aU: open: file not found
Jul  6 01:43:31 second named: transfer of 'domain.com/IN' from 192.168.2.2 00#53: failed while receiving responses: file not found
Jul  6 01:43:31 second named: transfer of 'domain.com/IN' from 192.168.2.2 00#53: end of transfer
Jul  6 01:43:40 second named: dumping master file: slaves/3.0/tmp-XXXXMRKP 4a: open: file not found
Jul  6 01:43:40 second named: transfer of '168.192.in-addr.arpa/IN' from 1 92.168.2.200#53: failed while receiving responses: file not found
Jul  6 01:43:40 second named: transfer of '168.192.in-addr.arpa/IN' from 1 92.168.2.200#53: end of transfer
Jul  6 01:44:43 second named: dumping master file: slaves/2.0/tmp-XXXXUUT2 eg: open: file not found
Jul  6 01:44:43 second named: transfer of 'domain.com/IN' from 192.168.2.2 00#53: failed while receiving responses: file not found
Jul  6 01:44:43 second named: transfer of 'domain.com/IN' from 192.168.2.2 00#53: end of transfer
Jul  6 01:45:18 second named: dumping master file: slaves/3.0/tmp-XXXXYaYb RU: open: file not found
Jul  6 01:45:18 second named: transfer of '168.192.in-addr.arpa/IN' from 1 92.168.2.200#53: failed while receiving responses: file not found
Jul  6 01:45:18 second named: transfer of '168.192.in-addr.arpa/IN' from 1 92.168.2.200#53: end of transfer
Jul  6 01:45:30 second named: dumping master file: slaves/3.0/tmp-XXXXfexx K6: open: file not found
Jul  6 01:45:30 second named: transfer of 'domain.com/IN' from 192.168.2.2 00#53: failed while receiving responses: file not found
Jul  6 01:45:30 second named: transfer of 'domain.com/IN' from 192.168.2.2 00#53: end of transfer
Jul  6 01:46:33 second named: dumping master file: slaves/2.0/tmp-XXXX57rq U6: open: file not found
Jul  6 01:46:33 second named: transfer of '168.192.in-addr.arpa/IN' from 1 92.168.2.200#53: failed while receiving responses: file not found
Jul  6 01:46:33 second named: transfer of '168.192.in-addr.arpa/IN' from 1 92.168.2.200#53: end of transfer
《解決方案》

原帖由 網中人 於 2007-7-8 17:23 發表 http://bbs.chinaunix.net/images/common/back.gif
tree /var/named 的結果如何?
額,我用的是RHEL 4.貌似沒有這個命令。。
《解決方案》

chown -R /var/named/chroot/var/named *
《解決方案》

沒有 tree 命令哦?
那用 find /var/named 也行
《解決方案》

as4 關閉 Selinux
《解決方案》

恩 我也碰到過類似問題,關了selinxu就ok了
《解決方案》

關SElinux是真解,我最近也被這個弄的頭都大了

[火星人 ] 在DNS從伺服器無法同步主伺服器已經有968次圍觀

http://coctec.com/docs/service/show-post-31760.html