Hello,
I'm quite new to this so I apologise if i have not seen a thread with this already. I did look! I seem to be having an issue with DNS bind service, it will not start but as far as i can see everything is correct. any help would be much appreciated x
● named.service - Berkeley Internet Name Domain (DNS)
Loaded: loaded (/usr/lib/systemd/system/named.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Mon 2020-03-23 09:37:50 GMT; 33min ago
Process: 27901 ExecStartPre=/bin/bash -c if [ ! "$DISABLE_ZONE_CHECKING" == "yes" ]; then /usr/sbin/named-checkconf -z "$NAMEDCONF"; else echo "Checking of zone files is disabled"; fi (code=exited, status=1/FAILURE)
Mar 23 09:37:50 metal.bridgetsarah.co.uk bash[27901]: zone 1.0.0.127.in-addr.arpa/IN: loaded serial 0
Mar 23 09:37:50 metal.bridgetsarah.co.uk bash[27901]: zone 0.in-addr.arpa/IN: loaded serial 0
Mar 23 09:37:50 metal.bridgetsarah.co.uk bash[27901]: zone metal.bridgetsarah.co.uk/IN: loaded serial 2020032165
Mar 23 09:37:50 metal.bridgetsarah.co.uk bash[27901]: zone ns1.bridgetsarah.co.uk/IN: loaded serial 2013071600
Mar 23 09:37:50 metal.bridgetsarah.co.uk bash[27901]: zone ns2.bridgetsarah.co.uk/IN: loaded serial 2013071600
Mar 23 09:37:50 metal.bridgetsarah.co.uk bash[27901]: zone roanate.co.uk/IN: loaded serial 2020032253
Mar 23 09:37:50 metal.bridgetsarah.co.uk systemd[1]: named.service: control process exited, code=exited status=1
Mar 23 09:37:50 metal.bridgetsarah.co.uk systemd[1]: Failed to start Berkeley Internet Name Domain (DNS).
Mar 23 09:37:50 metal.bridgetsarah.co.uk systemd[1]: Unit named.service entered failed state.
Mar 23 09:37:50 metal.bridgetsarah.co.uk systemd[1]: named.service failed.
the file----------------
//
// named.conf
//
// Provided by Red Hat bind package to configure the ISC BIND named(
DNS
// server as a caching only nameserver (as a any DNS resolver only).
//
// See /usr/share/doc/bind*/sample/ for example named configuration files.
//
// See the BIND Administrator's Reference Manual (ARM) for details about the
// configuration located in /usr/share/doc/bind-{version}/Bv9ARM.html
options {
listen-on port 53 { any; };
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";
recursing-file "/var/named/data/named.recursing";
secroots-file "/var/named/data/named.secroots";
allow-query { any; };
/*
- 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 no;
dnssec-enable yes;
dnssec-validation yes;
/* Path to ISC DLV key */
bindkeys-file "/etc/named.root.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 "bridgetsarah.co.uk" IN {
type master;
file "var/named/bridgetsarah.co.uk.db";
allow-update {none;};
};
include "/etc/named.rfc1912.zones";
include "/etc/named.root.key";
// zone metal.bridgetsarah.co.uk
zone "metal.bridgetsarah.co.uk" {type master; file "/var/named/metal.bridgetsarah.co.uk.db";};
// zone_end metal.bridgetsarah.co.uk
zone "ns1.bridgetsarah.co.uk" {type master;file "/var/named/ns1.bridgetsarah.co.uk.db";};
zone "ns2.bridgetsarah.co.uk" {type master;file "/var/named/ns2.bridgetsarah.co.uk.db";};
// zone roanate.co.uk
zone "roanate.co.uk" {type master; file "/var/named/roanate.co.uk.db";};
// zone_end roanate.co.uk
Topic: DNS bind issue /error (Read 3293 times)
