Messages

1

DNS / Re: DNS Failed to BIND after adding nameserver

« on: July 12, 2020, 10:59:38 PM »

I'm now only able to Activate BIND DNS if I disable named.service, and am seeing this status report;

WARNING!
● named.service - Berkeley Internet Name Domain (DNS)
   Loaded: loaded (/usr/lib/systemd/system/named.service; disabled; vendor preset: disabled)
   Active: active (running) since Mon 2020-07-13 00:56:00 SAST; 4s ago
  Process: 9481 ExecStop=/bin/sh -c /usr/sbin/rndc stop > /dev/null 2>&1 || /bin/kill -TERM $MAINPID (code=exited, status=0/SUCCESS)
  Process: 9493 ExecStart=/usr/sbin/named -u named -c ${NAMEDCONF} $OPTIONS (code=exited, status=0/SUCCESS)
  Process: 9491 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=0/SUCCESS)
 Main PID: 9496 (named)
   CGroup: /system.slice/named.service
           └─9496 /usr/sbin/named -u named -c /etc/named.conf

Jul 13 00:56:00 schoolcoding.dedicated.co.za named[9496]: network unreachable resolving 'ns2.centos-webpanel.com/A/IN': 2001:503:d2d::30#53
Jul 13 00:56:00 schoolcoding.dedicated.co.za named[9496]: network unreachable resolving 'ns2.centos-webpanel.com/AAAA/IN': 2001:503:d2d::30#53
Jul 13 00:56:00 schoolcoding.dedicated.co.za named[9496]: network unreachable resolving 'ns2.centos-webpanel.com/A/IN': 2001:503:a83e::2:30#53
Jul 13 00:56:00 schoolcoding.dedicated.co.za named[9496]: network unreachable resolving 'ns2.centos-webpanel.com/AAAA/IN': 2001:503:a83e::2:30#53
Jul 13 00:56:00 schoolcoding.dedicated.co.za named[9496]: network unreachable resolving 'ns2.centos-webpanel.com/A/IN': 2001:500:856e::30#53
Jul 13 00:56:00 schoolcoding.dedicated.co.za named[9496]: network unreachable resolving 'ns2.centos-webpanel.com/AAAA/IN': 2001:500:856e::30#53
Jul 13 00:56:00 schoolcoding.dedicated.co.za named[9496]: network unreachable resolving 'ns2.centos-webpanel.com/A/IN': 2001:501:b1f9::30#53
Jul 13 00:56:00 schoolcoding.dedicated.co.za named[9496]: network unreachable resolving 'ns2.centos-webpanel.com/AAAA/IN': 2001:501:b1f9::30#53
Jul 13 00:56:00 schoolcoding.dedicated.co.za named[9496]: network unreachable resolving 'ns2.centos-webpanel.com/A/IN': 2001:503:39c1::30#53
Jul 13 00:56:00 schoolcoding.dedicated.co.za named[9496]: network unreachable resolving 'ns2.centos-webpanel.com/AAAA/IN': 2001:503:39c1::30#53

Will the server function properly without the named.service?

2

DNS / Re: DNS Failed to BIND after adding nameserver

« on: July 11, 2020, 05:59:47 PM »

My nameservers are;

ns1.yourdomain.co.za resolves to 169.1.2.99
ns2.yourdomain.co.za resolves to 197.242.144.5

Here is the Status report of the BIND DNS failure;

×x
Logs
×WARNING!
● 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 Sat 2020-07-11 19:45:19 SAST; 2min 16s ago
  Process: 23669 ExecStart=/usr/sbin/named -u named -c ${NAMEDCONF} $OPTIONS (code=exited, status=1/FAILURE)
  Process: 23667 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=0/SUCCESS)

Jul 11 19:45:19 schoolcoding.dedicated.co.za named[23671]: using up to 21000 sockets
Jul 11 19:45:19 schoolcoding.dedicated.co.za named[23671]: loading configuration from '/etc/named.conf'
Jul 11 19:45:19 schoolcoding.dedicated.co.za named[23671]: reading built-in trust anchors from file '/etc/named.root.key'
Jul 11 19:45:19 schoolcoding.dedicated.co.za named[23671]: initializing GeoIP Country (IPv4) (type 1) DB
Jul 11 19:45:19 schoolcoding.dedicated.co.za named[23671]: GEO-106FREE 20180327 Build 1 Copyright (c) 2018 MaxMind Inc All Rights Reserved
Jul 11 19:45:19 schoolcoding.dedicated.co.za named[23671]: initializing GeoIP Country (IPv6) (type 12) DB
Jul 11 19:45:19 schoolcoding.dedicated.co.za systemd[1]: named.service: control process exited, code=exited status=1
Jul 11 19:45:19 schoolcoding.dedicated.co.za systemd[1]: Failed to start Berkeley Internet Name Domain (DNS).
Jul 11 19:45:19 schoolcoding.dedicated.co.za systemd[1]: Unit named.service entered failed state.
Jul 11 19:45:19 schoolcoding.dedicated.co.za systemd[1]: named.service failed.

Can anyone see any errors?

3

DNS / Re: DNS Failed to BIND after adding nameserver

« on: July 11, 2020, 08:48:10 AM »

Me too!

On Dashboard,
BIND DNS Server      Failed    Start  Restart Status  Report Issue

Status reveals;
named.service - Berkeley Internet Name Domain (DNS)
Loaded: loaded (/usr/lib/systemd/system/named.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code)

When I try to restart the service;

Job for named.service failed because the control process exited with error code. See "systemctl status named.service" and "journalctl -xe" for details.

Under Startup Services;

named.service is enabled

Under Services Monitoring (for systemd services);

named.service   
 Systemd status: failed (not ticked)


Any suggestions?