尝试启动区域传输时,我拒绝访问。
对于一个dig @ns.example.com example.com axfr我越来越
client 71.252.219.43#58392: zone transfer 'balticovo.eu/AXFR/IN' denied
组态:
/var/lib/named被chrooted。 named.conf中:
web:/var/lib/named/etc# cat named.conf options { directory "/etc"; pid-file "/var/run/named.pid"; statistics-file "/var/run/named.stats"; allow-transfer { 127.0.0.1; }; listen-on port 53 { any; }; listen-on-v6 port 53 { any; }; }; logging { category default { default_syslog; default_debug; }; category unmatched { null; }; channel default_syslog { syslog daemon; severity info; }; channel default_debug { file "named.run"; severity dynamic; }; channel default_stderr { stderr; severity info; }; channel null { null; }; }; zone "." { type hint; file "/etc/root.hints"; }; zone "localhost" { type master; file "/etc/localhost"; }; zone "0.0.127.in-addr.arpa" { type master; file "/etc/127.0.0"; }; zone "example.com" IN { type master; file "sites/example.com/forward.zone"; allow-transfer { 202.157.182.142; 71.252.219.43; }; allow-update { none; }; allow-query { any; }; zone-statistics yes; };
named -v输出BIND 9.6-ESV-R3 这个问题现在已经解决了。 我做了相当大的改变:
然后……当我在named.conf中进行更改并重新启动时,似乎之前的进程没有被杀死,但是新的进程产生了,并且在我的日志中有这样的行:
Jan 25 15:43:22 web named[18863]: listening on IPv6 interfaces, port 53 Jan 25 15:43:22 web named[18863]: binding TCP socket: address in use Jan 25 15:43:22 web named[18863]: listening on IPv4 interface lo, 127.0.0.1#53 Jan 25 15:43:22 web named[18863]: binding TCP socket: address in use Jan 25 15:43:22 web named[18863]: listening on IPv4 interface eth0, 10.3.0.10#53 Jan 25 15:43:22 web named[18863]: binding TCP socket: address in use ... Jan 25 15:43:22 web named[18863]: /etc/named.conf:12: couldn't add command channel 0.0.0.0#953: address in use
现在我做了killall named ,然后/etc/init.d/bind9 start ,一切顺利。
可能第三点解决了这个问题,因为当我改变named.conf时,实际上并没有使用最新的conf文件。
您的configuration文件仅显示127.0.0.1的允许传输选项,这可能是您的客户端被拒绝的原因。 你需要修改你的configuration来包含如下内容:
allow-transfer { 127.0.0.1; 71.252.219.43; };
(假设71.252.219.43是您期望能够进行区域转移的客户的地址。)