domain-name-system – BIND 9.9.3 slave更新：收到区域’domain’的通知：不具有权威性

我在从DNS服务器上正确加载区域时遇到问题.两台服务器都运行BIND 9.9.3-P2.

我已经服务了~150个区域,他们都正常工作.但是,当我添加另一个域时,从属服务器拒绝识别它.

这是主服务器上的区域规范：

zone "test.no" { type master; file "/var/lib/named/zones/test.zone"; };

这是奴隶的区域规范：

zone "test.no" { type slave; masters { master.ip; }; file "/var/lib/named/zones/test.zone"; };

当我在主服务器上执行rndc重新加载时,从服务器获取通知,从主服务器传输区域并且不会抱怨.这是来自奴隶的日志：

27-Mar-2014 10:30:15.146 zone test.no/IN: no master file
27-Mar-2014 10:30:15.146 zone_settimer: zone test.no/IN: enter
27-Mar-2014 10:30:15.157 dns_zone_maintenance: zone test.no/IN: enter
27-Mar-2014 10:30:15.158 zone_settimer: zone test.no/IN: enter
27-Mar-2014 10:30:15.166 zone_timer: zone test.no/IN: enter
27-Mar-2014 10:30:15.166 zone_maintenance: zone test.no/IN: enter
27-Mar-2014 10:30:15.166 queue_soa_query: zone test.no/IN: enter
27-Mar-2014 10:30:15.166 zone_settimer: zone test.no/IN: enter
27-Mar-2014 10:30:15.166 soa_query: zone test.no/IN: enter
27-Mar-2014 10:30:15.170 refresh_callback: zone test.no/IN: enter
27-Mar-2014 10:30:15.170 refresh_callback: zone test.no/IN: serial: new 2014031901,old not loaded
27-Mar-2014 10:30:15.170 queue_xfrin: zone test.no/IN: enter
27-Mar-2014 10:30:15.171 zone test.no/IN: Transfer started.
27-Mar-2014 10:30:15.171 zone test.no/IN: no database exists yet,requesting AXFR of initial version from x.x.x.x#53
27-Mar-2014 10:30:15.171 transfer of 'test.no/IN' from x.x.x.x#53: connected using x.x.x.y#59644
27-Mar-2014 10:30:15.179 zone test.no/IN: zone transfer finished: success
27-Mar-2014 10:30:15.179 zone test.no/IN: transferred serial 2014031901
27-Mar-2014 10:30:15.179 zone_needdump: zone test.no/IN: enter
27-Mar-2014 10:30:15.179 zone_settimer: zone test.no/IN: enter
27-Mar-2014 10:30:15.179 zone_settimer: zone test.no/IN: enter
27-Mar-2014 10:30:15.179 transfer of 'test.no/IN' from x.x.x.x#53: Transfer completed: 1 messages,6 records,197 bytes,0.007 secs (28142 bytes/sec)
27-Mar-2014 10:30:15.180 zone_timer: zone test.no/IN: enter
27-Mar-2014 10:30:15.180 zone_maintenance: zone test.no/IN: enter
27-Mar-2014 10:30:15.180 zone test.no/IN: sending notifies (serial 2014031901)
27-Mar-2014 10:30:15.186 zone_dump: zone test.no/IN: enter
27-Mar-2014 10:30:15.186 zone_settimer: zone test.no/IN: enter
27-Mar-2014 10:30:15.186 zone_gotwritehandle: zone test.no/IN: enter
27-Mar-2014 10:30:15.186 decrement_reference: delete from rbt: 0x9a725d8 test.no
27-Mar-2014 10:30:15.187 dump_done: zone test.no/IN: enter

并且/var/lib/named/zones/test.zone在slave上创建并填充：

-rw-r--r-- 1 named named 250 Mar 27 10:30 test.zone

一切都很好！但是,在我增加主服务器上的序列并进行另一次重新加载后,我得到了同样的错误：

27-Mar-2014 10:30:51.405 client x.x.x.x#42033: received notify for zone 'test.no': not authoritative

test.no区域是我尝试使用相同错误的第二个区域,配置与其他工作区域具有相同的语法.

主机上显示的实际区域文件：

$TTL 1h0m6s
@       IN      SOA     ns1.domain.no. postmaster.domain.no. (
                        2014031902      ; serial,todays date + todays serial #
                        1H              ; refresh,seconds
                        2H              ; retry,seconds
                        2D              ; expire,seconds
                        1H )            ; minimum,seconds

                NS      ns1.domain.no.
                NS      ns2.domain.no.
                TXT     "test.no"


test        A     10.0.0.1

解决方法

为了其他任何有这个问题并且最终来自Google的人的利益,对我来说问题是由于我使用BIND视图引起的.

我已经配置了多个视图,假设BIND会将所有匹配的视图合并为一个视图,但实际上它会选择第一个匹配视图并仅使用该视图,而忽略所有其他视图.因此,客户端只看到了我的一小部分区域,因此视图中缺失的那些区域将成为非权威性的.

通过将所有内容都粘贴到包含文件中并使用它们来确保每个视图都完全完整,我的问题得以解决.