refused notify from non-master报错
Apr 19 12:12:10 localhost named[6935]: client 10.254.*.*#60898: received notify for zone 'retail-tek.com'
Apr 19 12:12:10 localhost named[6935]: zone retail-tek.com/IN: refused notify from non-master: 10.254.*.*#60898
配置文件里加入
[root@landnsbak ~]# vi /var/named/chroot/etc/named.conf
allow-notify { 10.254.*.*; };
重启服务
Apr 19 14:52:20 landnsbak named[29840]: client *.*.*.*#30345: view localhost_resolver: received notify for zone 'retail-tek.com'
Apr 19 14:52:20 landnsbak named[29840]: zone retail-tek.com/IN/localhost_resolver: notify from *.*.*.*#30345: zone is up to date
==============================================================================================
I was adding a new slave DNS server the other day on bind 9.3 and I was getting this error “refused notify from non-master”. It seems that if you are using bind 9.3 it tries to send a notify to itself even if it is a slave. In the options section of named.conf you need to add an allow-notify for it’s own IP. Substitute 192.168.0.1 for your server’s IP.
options {
//otherstuff
allow-notify {192.168.0.1;};
};