Linux CentOS DNS: Failed to start Berkeley Internet Name Domain (DNS)

-- Logs begin at Thu 2015-07-16 15:05:55 CEST, end at Thu 2015-07-16 15:25:40 CEST. --
Jul 16 15:25:40 CentDNS named-checkconf[11998]: zone 1.168.192.in-addr.arpa/IN: not loaded due to errors.
Jul 16 15:25:40 CentDNS named-checkconf[11998]: _default/1.168.192.in-addr.arpa/IN: file not found
Jul 16 15:25:40 CentDNS named-checkconf[11998]: zone localhost.localdomain/IN: loaded serial 0
Jul 16 15:25:40 CentDNS named-checkconf[11998]: zone localhost/IN: loaded serial 0
Jul 16 15:25:40 CentDNS named-checkconf[11998]: 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/IN: loaded serial 0
Jul 16 15:25:40 CentDNS named-checkconf[11998]: zone 1.0.0.127.in-addr.arpa/IN: loaded serial 0
Jul 16 15:25:40 CentDNS named-checkconf[11998]: zone 0.in-addr.arpa/IN: loaded serial 0
Jul 16 15:25:40 CentDNS systemd[1]: named.service: control process exited, code=exited status=1
-- Subject: Unit named.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit named.service has failed.
--
-- The result is failed.
Jul 16 15:25:40 CentDNS systemd[1]: Unit named.service entered failed state.

named.conf
Provided by Red Hat bind package to configure the ISC BIND named(8) 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; 172.31.3.10; };
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; 172.31.3.0/24; };

/*
- 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 auto;

/* 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";
};

zone"CentDNS.local" IN {
type master;
file "forward.CentDNS";
allow-update { none; };
};
zone"1.168.192.in-addr.arpa" IN {
type master;
file "reverse.CentDNS";
allow-update { none; };
};

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

$TTL 86400
@ IN SOA ns1.CentDNS.local. root.CentDNS.local. (
2014072701 ;Serial
3600 ;Refresh
1800 ;Retry
604800 ;Expire
86400 ;Minimum TTL
)
@ IN NS ns1.CentDNS.local.
@ IN A 172.31.3.254
@ IN A 172.31.3.10
gw IN A 172.31.3.254
ns1 IN A 172.31.3.10

$TTL 86400
@ IN SOA ns1.CentDNS.local. root.CentDNS.local. (
2014072701 ;Serial
3600 ;Refresh
1800 ;Retry
604800 ;Expire
86400 ;Minimum TTL
)
@ IN NS ns1.CentDNS.local.
@ IN PTR CentDNS.local.
gw IN A 172.31.3.254
ns1 IN A 172.31.3.10

254 IN PTR gw.CentDNS.local.
10 IN PTR ns1.CentDNS.local.