dns-bind9.3 - refused notify from non-master
2017-04-19 14:58
597 查看
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;};
};
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;};
};
相关文章推荐
- 遇到 bind DNS 的 Master 与 Slave 不能同步更新问题
- Caused by: java.net.ConnectException: Call From master/192.168.199.130 to master:9000 failed on connection exception: java.net.ConnectException: Connection refused; For more details see: http://wiki.
- bind9 dns智能解析 for windows 2003 master/slave dns配置
- BIND Master/Slave DNS 與 View 的搭配
- BIND服务基础及DNS Master服务器配置步骤
- BIND服务基础及DNS Master服务器配置步骤
- 基于BIND的DNS名字服务器的配置文件详解
- Brad wants to hear from non-english speaking .net developers
- 使用BIND安装智能DNS服务器(一)---基本的主从DNS服务器搭建
- MySQL之Got fatal error 1236 from master when reading data from binary log
- bind搭建dns
- Conversion from 'void*' to pointer to non-'void' requires an explicit cast
- Linux与云计算——第二阶段 第四章:DNS服务器架设1-安装BIND
- RHEL4-DNS服务(二)bind安装后的DNS服务文件及详解
- DNS安装配置全过程(BIND)
- How To Upgrade ASM from 10.2 to 11.1 (single Instance configuration -Non-RAC)
- DNS&BIND——DNS的ACL和视图
- DNS&BIND——源码编译bind9和DNS的压力测试
- 初试DNS(bind9搭建)--Centos6平台
- DNS(bind)服务器安装和配置