[BlueOnyx:23245] Update killed DNS server!!

Colin Jack colin at mainline.co.uk
Wed Sep 18 02:51:46 -05 2019


Good morning all.

This update has killed my DNS server!
It is a Virtbiz VPS so will open a ticket with them but thought to post here in case anybody else sees this problem (and hopefully a solution).

[root at iris ~]# systemctl status named.service
* 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 Wed 2019-09-18 07:46:37 UTC; 13s ago
  Process: 31435 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)

Sep 18 07:46:37 iris.mainline.co.uk bash[31435]: zone mainline.co.uk/IN: loading from master file db.mainline.co.uk failed: file not found
Sep 18 07:46:37 iris.mainline.co.uk bash[31435]: zone mainline.co.uk/IN: not loaded due to errors.
Sep 18 07:46:37 iris.mainline.co.uk bash[31435]: _default/mainline.co.uk/IN: file not found
Sep 18 07:46:37 iris.mainline.co.uk bash[31435]: zone 249.67.208.in-addr.arpa/IN: loading from master file db.249.67.208.in-addr.arpa failed: file not found
Sep 18 07:46:37 iris.mainline.co.uk bash[31435]: zone 249.67.208.in-addr.arpa/IN: not loaded due to errors.
Sep 18 07:46:37 iris.mainline.co.uk bash[31435]: _default/249.67.208.in-addr.arpa/IN: file not found
Sep 18 07:46:37 iris.mainline.co.uk systemd[1]: named.service: control process exited, code=exited status=1
Sep 18 07:46:37 iris.mainline.co.uk systemd[1]: Failed to start Berkeley Internet Name Domain (DNS).
Sep 18 07:46:37 iris.mainline.co.uk systemd[1]: Unit named.service entered failed state.
Sep 18 07:46:37 iris.mainline.co.uk systemd[1]: named.service failed.

Regards

Colin




More information about the Blueonyx mailing list