redhat搭建DNS解析时出现错误(已解决)

vermouth

服务器 setenforce 0,客户端 telnet 192.168.202.5 53

yoknbububu

回复 11# vermouth


    我还没配客户端啊。我在服务器上测试解析不了就没配客户端了

FaintKnowledge

回复 12# yoknbububu


使用原来的配置文件,把从重启到完成 message中所有的日志贴出来看看?

yoknbububu

回复 13# FaintKnowledge


    [root@localhost log]# cat /var/log/messages
Apr 20 04:02:03 localhost syslogd 1.4.1: restart.
Apr 20 04:06:04 localhost init: Trying to re-exec init
Apr 20 06:58:40 localhost avahi-daemon[3717]: Withdrawing address record for 192.168.202.5 on eth0.
Apr 20 06:58:40 localhost avahi-daemon[3717]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.202.5.
Apr 20 06:58:40 localhost avahi-daemon[3717]: iface.c: interface_mdns_mcast_join() called but no local address available.
Apr 20 06:58:40 localhost avahi-daemon[3717]: Interface eth0.IPv4 no longer relevant for mDNS.
Apr 20 06:58:40 localhost avahi-daemon[3717]: Withdrawing address record for fe80::20c:29ff:feaa:6701 on eth0.
Apr 20 06:58:40 localhost avahi-daemon[3717]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::20c:29ff:feaa:6701.
Apr 20 06:58:40 localhost avahi-daemon[3717]: iface.c: interface_mdns_mcast_join() called but no local address available.
Apr 20 06:58:40 localhost avahi-daemon[3717]: Interface eth0.IPv6 no longer relevant for mDNS.
Apr 20 06:58:40 localhost dhcpd: receive_packet failed on eth0: Network is down
Apr 20 06:58:42 localhost avahi-daemon[3717]: New relevant interface eth0.IPv6 for mDNS.
Apr 20 06:58:42 localhost avahi-daemon[3717]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::20c:29ff:feaa:6701.
Apr 20 06:58:42 localhost avahi-daemon[3717]: Registering new address record for fe80::20c:29ff:feaa:6701 on eth0.
Apr 20 06:58:45 localhost avahi-daemon[3717]: New relevant interface eth0.IPv4 for mDNS.
Apr 20 06:58:45 localhost avahi-daemon[3717]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.202.5.
Apr 20 06:58:45 localhost avahi-daemon[3717]: Registering new address record for 192.168.202.5 on eth0.
Apr 20 06:59:12 localhost named[26989]: shutting down: flushing changes
Apr 20 06:59:12 localhost named[26989]: stopping command channel on 127.0.0.1#953
Apr 20 06:59:12 localhost named[26989]: stopping command channel on ::1#953
Apr 20 06:59:12 localhost named[26989]: no longer listening on ::1#53
Apr 20 06:59:12 localhost named[26989]: no longer listening on 127.0.0.1#53
Apr 20 06:59:12 localhost named[26989]: no longer listening on 192.168.202.5#53
Apr 20 06:59:12 localhost named[26989]: exiting
Apr 20 06:59:14 localhost named[5307]: starting BIND 9.3.3rc2 -u named -t /var/named/chroot
Apr 20 06:59:14 localhost named[5307]: found 1 CPU, using 1 worker thread
Apr 20 06:59:14 localhost named[5307]: loading configuration from '/etc/named.conf'
Apr 20 06:59:14 localhost named[5307]: /etc/named.conf:34: when using 'view' statements, all zones must be in views
Apr 20 06:59:14 localhost named[5307]: listening on IPv6 interface lo, ::1#53
Apr 20 06:59:14 localhost named[5307]: listening on IPv4 interface lo, 127.0.0.1#53
Apr 20 06:59:14 localhost named[5307]: listening on IPv4 interface eth0, 192.168.202.5#53
Apr 20 06:59:14 localhost named[5307]: command channel listening on 127.0.0.1#953
Apr 20 06:59:14 localhost named[5307]: command channel listening on ::1#953
Apr 20 06:59:14 localhost named[5307]: zone 0.in-addr.arpa/IN/localhost_resolver: loaded serial 42
Apr 20 06:59:14 localhost named[5307]: zone 0.0.127.in-addr.arpa/IN/localhost_resolver: loaded serial 1997022700
Apr 20 06:59:14 localhost named[5307]: zone 255.in-addr.arpa/IN/localhost_resolver: loaded serial 42
Apr 20 06:59:14 localhost named[5307]: 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.ip6.arpa/IN/localhost_resolver: loaded serial 1997022700
Apr 20 06:59:14 localhost named[5307]: zone localdomain/IN/localhost_resolver: loaded serial 42
Apr 20 06:59:14 localhost named[5307]: zone localhost/IN/localhost_resolver: loaded serial 42
Apr 20 06:59:14 localhost named[5307]: running

FaintKnowledge

回复 14# yoknbububu


检查下权限设置，都改称named用户named组

yoknbububu

回复 15# FaintKnowledge


    -rw-r----- 1 root  named  438 Apr 19 07:07 192.168.202.zone
drwxrwx--- 2 named named 4096 Mar 16 22:03 data
-rw-r----- 1 root  named  198 Jan 16  2007 localdomain.zone
-rw-r----- 1 root  named  195 Jan 16  2007 localhost.zone
-rw-r----- 1 root  named  489 Mar 17 00:41 named.0.168.192.arpa.zone
-rw-r----- 1 root  named  427 Jan 16  2007 named.broadcast
-rw-r----- 1 root  named 2518 Jan 16  2007 named.ca
-rw-r----- 1 root  named  424 Jan 16  2007 named.ip6.local
-rw-r----- 1 root  named  426 Jan 16  2007 named.local
-rw-r----- 1 root  named  427 Jan 16  2007 named.zero
-rw-r----- 1 root  named  219 Apr 19 07:07 sales.com.zone
drwxrwx--- 2 named named 4096 Jul 27  2004 slaves
-rw-r----- 1 root  root   214 Apr 19 06:35 smile.com.zone


改了。我的是sales.com.zone和192.168.202.zone这两个文件

marsaber

-rw-r----- 1 root  root   214 Apr 19 06:35 smile.com.zone

chown -R root.named smile.com.zone
重启named服务，再测试。

bworld

你是用虚拟机装的么？？如果是用虚拟机装的，你先把宿主机上的防火墙关了，如果还不行，就查服务器日志，一般named启动的只要配置语法没问题都可以启动，真正的问题都是反映在日志里面的。。。

firwood

当你做对的时候，没有人会记得；当你做错的时候，连呼吸都是错。

支持一下










signature..................................
天才相师

yoknbububu

回复 17# marsaber


    但是我的正向解析文件是“sales .com.zone”哦。这个也要改嘛？