Author Topic: BIND DNS Server Failing to Start on Amazon LightSail Instance - Log Attached  (Read 349 times)

0 Members and 1 Guest are viewing this topic.

Offline
*
● 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 Fri 2019-01-25 09:17:33 UTC; 55s ago
  Process: 26229 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)

Jan 25 09:17:33 ip-174-26-3-17.ec2.internal bash[26229]: zone zoxus.tech/IN: loaded serial 2019012001
Jan 25 09:17:33 ip-174-26-3-17.ec2.internal bash[26229]: zone ns1.filmymirror-web.com/IN: loaded serial 2013071600
Jan 25 09:17:33 ip-174-26-3-17.ec2.internal bash[26229]: zone ns2.filmymirror-web.com/IN: loaded serial 2013071600
Jan 25 09:17:33 ip-174-26-3-17.ec2.internal bash[26229]: zone ns1.zoxus.tech/IN: loaded serial 2013071600
Jan 25 09:17:33 ip-174-26-3-17.ec2.internal bash[26229]: zone ns2.zoxus.tech/IN: loaded serial 2013071600
Jan 25 09:17:33 ip-174-26-3-17.ec2.internal systemd[1]: named.service: control process exited, code=exited status=1
Jan 25 09:17:33 ip-174-26-3-17.ec2.internal bash[26229]: zone codexvo.com/IN: loaded serial 2018071600
Jan 25 09:17:33 ip-174-26-3-17.ec2.internal systemd[1]: Failed to start Berkeley Internet Name Domain (DNS).
Jan 25 09:17:33 ip-174-26-3-17.ec2.internal systemd[1]: Unit named.service entered failed state.
Jan 25 09:17:33 ip-174-26-3-17.ec2.internal systemd[1]: named.service failed.

Offline
***
The 'named-checkconf' is pointing error.
Execute 'named-checkconf', and check your /var/log/messages file.

Regards,
Netino