当前位置: 技术问答>linux和unix
debian 下安装设置了bind9之后运行named -g出现如下提示不运行了
来源: 互联网 发布时间：2016-11-13
本文导语: 请问debian 下安装设置了bind9之后运行named -g出现如下提示不运行了，是怎么回事？谢谢！ 03-Mar-2011 17:10:39.492 starting BIND 9.8.0 -g 03-Mar-2011 17:10:39.492 built with '--prefix=/data/bind9.8' 03-Mar-2011 17:10:39.492 using up to 4096...
请问debian 下安装设置了bind9之后运行named -g出现如下提示不运行了，是怎么回事？谢谢！
03-Mar-2011 17:10:39.492 starting BIND 9.8.0 -g
03-Mar-2011 17:10:39.492 built with '--prefix=/data/bind9.8'
03-Mar-2011 17:10:39.492 using up to 4096 sockets
03-Mar-2011 17:10:39.497 loading configuration from '/data/bind9.8/etc/named.conf'
03-Mar-2011 17:10:39.497 reading built-in trusted keys from '/data/bind9.8/etc/named.conf'
03-Mar-2011 17:10:39.497 reading built-in trusted keys from file '/data/bind9.8/etc/bind.keys'
03-Mar-2011 17:10:39.498 using default UDP/IPv4 port ran port range: [1024, 65535]
03-Mar-2011 17:10:39.498 using default UDP/IPv6 port range: [1024, 65535]
03-Mar-2011 17:10:39.503 listening on IPv4 interface eth0, 192.168.10.152#53
03-Mar-2011 17:10:39.503 generating session key for key for dynamic DNS
03-Mar-2011 17:10:39.507 set up managed keys zone for view _default, file 'managed-keys.bind'
03-Mar-2011 17:10:39.507 automatic empty zone: 0.IN-ADDR.ARPA
03-Mar-2011 17:10:39.507 automatic empty zone: 127.IN-ADDR.ARPA
03-Mar-2011 17:10:39.507 automatic empty zone: 254.169.IN-ADDR.ARPA
03-Mar-2011 17:10:39.507 automatic empty zone: 2.0.192.IN-ADDR.ARPA
03-Mar-2011 17:10:39.507 automatic empty zone: 100.51.198.IN-ADDR.ARPA
03-Mar-2011 17:10:39.507 automatic empty zone: 113.0.203.IN-ADDR.ARPA
03-Mar-2011 17:10:39.507 automatic empty zone: 255.255.255.255.IN-ADDR.ARPA
03-Mar-2011 17:10:39.507 automatic empty zone: 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
03-Mar-2011 17:10:39.507 automatic empty zone: 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
03-Mar-2011 17:10:39.507 automatic empty zone: D.F.IP6.ARPA
03-Mar-2011 17:10:39.507 automatic empty zone: 8.E.F.IP6.ARPA
03-Mar-2011 17:10:39.507 automatic empty zone: 9.E.F.IP6.ARPA
03-Mar-2011 17:10:39.507 automatic empty zone: A.E.F.IP6.ARPA
03-Mar-2011 17:10:39.507 automatic empty zone: B.E.F.IP6.ARPA
03-Mar-2011 17:10:39.507 automatic empty zone: 8.B.D.0.1.0.0.2.IP6.ARPA
03-Mar-2011 17:10:39.509 /data/bind9.8/etc/named.conf:14: couldn't add command channel 127.0.0.1#953: address not available
03-Mar-2011 17:10:39.510 ignoring config file logging statement due to -g option
03-Mar-2011 17:10:39.511 zone 0.0.127.in-addr.arpa/IN: loaded serial 1
03-Mar-2011 17:10:39.511 zone 10.168.192.in-addr.arpa/IN: loaded serial 1
03-Mar-2011 17:10:39.512 zone localdomain/IN: loaded serial 1
03-Mar-2011 17:10:39.512 zone localhost/IN: loaded serial 1
03-Mar-2011 17:10:39.512 managed-keys-zone ./IN: loaded serial 0
03-Mar-2011 17:10:39.513 running
03-Mar-2011 17:10:39.492 starting BIND 9.8.0 -g
03-Mar-2011 17:10:39.492 built with '--prefix=/data/bind9.8'
03-Mar-2011 17:10:39.492 using up to 4096 sockets
03-Mar-2011 17:10:39.497 loading configuration from '/data/bind9.8/etc/named.conf'
03-Mar-2011 17:10:39.497 reading built-in trusted keys from '/data/bind9.8/etc/named.conf'
03-Mar-2011 17:10:39.497 reading built-in trusted keys from file '/data/bind9.8/etc/bind.keys'
03-Mar-2011 17:10:39.498 using default UDP/IPv4 port ran port range: [1024, 65535]
03-Mar-2011 17:10:39.498 using default UDP/IPv6 port range: [1024, 65535]
03-Mar-2011 17:10:39.503 listening on IPv4 interface eth0, 192.168.10.152#53
03-Mar-2011 17:10:39.503 generating session key for key for dynamic DNS
03-Mar-2011 17:10:39.507 set up managed keys zone for view _default, file 'managed-keys.bind'
03-Mar-2011 17:10:39.507 automatic empty zone: 0.IN-ADDR.ARPA
03-Mar-2011 17:10:39.507 automatic empty zone: 127.IN-ADDR.ARPA
03-Mar-2011 17:10:39.507 automatic empty zone: 254.169.IN-ADDR.ARPA
03-Mar-2011 17:10:39.507 automatic empty zone: 2.0.192.IN-ADDR.ARPA
03-Mar-2011 17:10:39.507 automatic empty zone: 100.51.198.IN-ADDR.ARPA
03-Mar-2011 17:10:39.507 automatic empty zone: 113.0.203.IN-ADDR.ARPA
03-Mar-2011 17:10:39.507 automatic empty zone: 255.255.255.255.IN-ADDR.ARPA
03-Mar-2011 17:10:39.507 automatic empty zone: 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
03-Mar-2011 17:10:39.507 automatic empty zone: 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
03-Mar-2011 17:10:39.507 automatic empty zone: D.F.IP6.ARPA
03-Mar-2011 17:10:39.507 automatic empty zone: 8.E.F.IP6.ARPA
03-Mar-2011 17:10:39.507 automatic empty zone: 9.E.F.IP6.ARPA
03-Mar-2011 17:10:39.507 automatic empty zone: A.E.F.IP6.ARPA
03-Mar-2011 17:10:39.507 automatic empty zone: B.E.F.IP6.ARPA
03-Mar-2011 17:10:39.507 automatic empty zone: 8.B.D.0.1.0.0.2.IP6.ARPA
03-Mar-2011 17:10:39.509 /data/bind9.8/etc/named.conf:14: couldn't add command channel 127.0.0.1#953: address not available
03-Mar-2011 17:10:39.510 ignoring config file logging statement due to -g option
03-Mar-2011 17:10:39.511 zone 0.0.127.in-addr.arpa/IN: loaded serial 1
03-Mar-2011 17:10:39.511 zone 10.168.192.in-addr.arpa/IN: loaded serial 1
03-Mar-2011 17:10:39.512 zone localdomain/IN: loaded serial 1
03-Mar-2011 17:10:39.512 zone localhost/IN: loaded serial 1
03-Mar-2011 17:10:39.512 managed-keys-zone ./IN: loaded serial 0
03-Mar-2011 17:10:39.513 running
|
03-Mar-2011 17:10:39.507 automatic empty zone: 8.B.D.0.1.0.0.2.IP6.ARPA
03-Mar-2011 17:10:39.509 /data/bind9.8/etc/named.conf:14: couldn't add command channel 127.0.0.1#953: address not available
看看这是不是有问题？
03-Mar-2011 17:10:39.509 /data/bind9.8/etc/named.conf:14: couldn't add command channel 127.0.0.1#953: address not available
看看这是不是有问题？
|
把named.conf和localdomain.zone文件贴上来看看
|
虽然过程中出现了一些问题 单从最后一句看 应该是在运行哦
本站(WWW.)旨在分享和传播互联网科技相关的资讯和技术，将尽最大努力为读者提供更好的信息聚合和浏览方式。
本站(WWW.)站内文章除注明原创外，均为转载、整理或搜集自网络。欢迎任何形式的转载，转载请注明出处。
本站(WWW.)站内文章除注明原创外，均为转载、整理或搜集自网络。欢迎任何形式的转载，转载请注明出处。