BIND 安装完成后无法启动 请问这是什么问题

chenskyo

安装好以后无法启动bind 请高手帮忙解决下  给我说说那出了问题 谢谢拉



启动就报错

root@localhost ~]# service named restart
Redirecting to /bin/systemctl restart  named.service
Job for named.service failed. See 'systemctl status named.service' and 'journalctl -xn' for details.

日志
Jun 17 10:04:08 localhost systemd: Starting Generate rndc key for BIND (DNS)...
Jun 17 10:04:08 localhost systemd: Started Generate rndc key for BIND (DNS).
Jun 17 10:04:08 localhost systemd: Starting Berkeley Internet Name Domain (DNS)...
Jun 17 10:04:08 localhost named-checkconf: /etc/named.conf:34: expected unquoted string near ';'
Jun 17 10:04:08 localhost systemd: named.service: control process exited, code=exited status=1
Jun 17 10:04:08 localhost systemd: Failed to start Berkeley Internet Name Domain (DNS).
Jun 17 10:04:08 localhost systemd: Unit named.service entered failed state.



安装
[root@localhost ~]# rpm -q bind
bind-9.9.4-18.el7_1.1.x86_64
[root@localhost ~]#

[root@localhost ~]# rpm -qa | grep bind
keybinder3-0.3.0-1.el7.x86_64
bind-license-9.9.4-18.el7_1.1.noarch
bind-sdb-chroot-9.9.4-18.el7_1.1.x86_64
bind-chroot-9.9.4-18.el7_1.1.x86_64
bind-dyndb-ldap-6.0-2.el7.x86_64
PackageKit-device-rebind-0.8.9-11.el7.centos.x86_64
bind-9.9.4-18.el7_1.1.x86_64
bind-devel-9.9.4-18.el7_1.1.x86_64
rpcbind-0.2.0-26.el7.x86_64
bind-lite-devel-9.9.4-18.el7_1.1.x86_64
bind-libs-9.9.4-18.el7_1.1.x86_64
bind-libs-lite-9.9.4-18.el7_1.1.x86_64
bind-utils-9.9.4-18.el7_1.1.x86_64
bind-sdb-9.9.4-18.el7_1.1.x86_64
[root@localhost ~]#

yyu0378

系统换systemd管理服务了，建议你用它提示的命令执行systemctl restart  named.service

chenskyo

谢谢 朋友 先试下

chenskyo

bind 是启动了 但没办法提供转发解析

chenyx

Jun 17 10:04:08 localhost named-checkconf: /etc/named.conf:34: expected unquoted string near ';'

检测你的named配置文件

chenskyo

启动不了 第一次接触 Cent OS 请教下大家  谢谢

[root@localhost ~]# systemctl status named.service
named.service - Berkeley Internet Name Domain (DNS)
   Loaded: loaded (/usr/lib/systemd/system/named.service; disabled)
   Active: failed (Result: exit-code) since 三 2015-06-17 10:33:15 CST; 7s ago
  Process: 27973 ExecStartPre=/usr/sbin/named-checkconf -z /etc/named.conf (code=exited, status=1/FAILURE)

6月 17 10:33:15 bogon named-checkconf[27973]: /etc/named.conf:34: expected unquoted string near ';'
6月 17 10:33:15 bogon systemd[1]: named.service: control process exited, code=exited status=1
6月 17 10:33:15 bogon systemd[1]: Failed to start Berkeley Internet Name Domain (DNS).
6月 17 10:33:15 bogon systemd[1]: Unit named.service entered failed state.
[root@localhost ~]#

chenskyo

这是不是代表 named.conf 文件34行 多了；号？？？？

chenskyo

这是我的 named.conf 文件  请文那多了；  找了半天没找到  就做了个 转发DNS解析
//
// named.conf
//
// Provided by Red Hat bind package to configure the ISC BIND named( DNS
// server as a caching only nameserver (as a localhost DNS resolver only).
//
// See /usr/share/doc/bind*/sample/ for example named configuration files.
//

options {
        listen-on port 53 { 127.0.0.1; };
        listen-on-v6 port 53 { ::1; };
        directory         "/var/named";
        dump-file         "/var/named/data/cache_dump.db";
        statistics-file "/var/named/data/named_stats.txt";
        memstatistics-file "/var/named/data/named_mem_stats.txt";
        allow-query     { localhost; };

        /*
         - If you are building an AUTHORITATIVE DNS server, do NOT enable recursion.
         - If you are building a RECURSIVE (caching) DNS server, you need to enable
           recursion.
         - If your recursive DNS server has a public IP address, you MUST enable access
           control to limit queries to your legitimate users. Failing to do so will
           cause your server to become part of large scale DNS amplification
           attacks. Implementing BCP38 within your network would greatly
           reduce such attack surface
        */
        recursion yes;

        dnssec-enable yes;
        dnssec-validation yes;
        dnssec-lookaside no;
       forward;
       forwarders{
                    8.8.8.8;
};

      
        /* Path to ISC DLV key */
        bindkeys-file "/etc/named.iscdlv.key";

        managed-keys-directory "/var/named/dynamic";

        pid-file "/run/named/named.pid";
        session-keyfile "/run/named/session.key";
};

logging {
        channel default_debug {
                file "data/named.run";
                severity dynamic;
        };
};

zone "." IN {
        type hint;
        file "named.ca";
};

include "/etc/named.rfc1912.zones";
include "/etc/named.root.key";

chenskyo

在线等高手帮忙解答

yyu0378

forwarders{8.8.8.8; };这样试试看