-- A start job for unit named.service has begun execution.
--
-- The job identifier is 28649.
Apr 21 11:36:07
ws.linuxlighthouse.com bash[1451129]: zone localhost.localdomain/IN: has
0 SOA records
Apr 21 11:36:07
ws.linuxlighthouse.com bash[1451129]: zone localhost.localdomain/IN: has
no NS records
Apr 21 11:36:07
ws.linuxlighthouse.com bash[1451129]: zone localhost.localdomain/IN: not
loaded due to errors.
Apr 21 11:36:07
ws.linuxlighthouse.com bash[1451129]: _default/localhost.localdomain/IN:
bad zone
Apr 21 11:36:07
ws.linuxlighthouse.com bash[1451129]: zone localhost/IN: has 0 SOA
records
Apr 21 11:36:07
ws.linuxlighthouse.com bash[1451129]: zone localhost/IN: has no NS
records
Apr 21 11:36:07
ws.linuxlighthouse.com bash[1451129]: zone localhost/IN: not loaded due
to errors.
Apr 21 11:36:07
ws.linuxlighthouse.com bash[1451129]: _default/localhost/IN: bad zone
Apr 21 11:36:07
ws.linuxlighthouse.com bash[1451129]: 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: has 0 SOA
records
Apr 21 11:36:07
ws.linuxlighthouse.com bash[1451129]: 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: has no NS
records
Apr 21 11:36:07
ws.linuxlighthouse.com bash[1451129]: 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: not loaded
due to errors.
Apr 21 11:36:07
ws.linuxlighthouse.com bash[1451129]:
_default/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: bad
zone
Apr 21 11:36:07
ws.linuxlighthouse.com bash[1451129]: zone 1.0.0.127.in-addr.arpa/IN: has
0 SOA records
Apr 21 11:36:07
ws.linuxlighthouse.com bash[1451129]: zone 1.0.0.127.in-addr.arpa/IN: has
no NS records
Apr 21 11:36:07
ws.linuxlighthouse.com bash[1451129]: zone 1.0.0.127.in-addr.arpa/IN: not
loaded due to errors.
Apr 21 11:36:07
ws.linuxlighthouse.com bash[1451129]: _default/1.0.0.127.in-addr.arpa/IN:
bad zone
Apr 21 11:36:07
ws.linuxlighthouse.com bash[1451129]: zone 0.in-addr.arpa/IN: loaded
serial 0
Apr 21 11:36:07
ws.linuxlighthouse.com systemd[1]: named.service: Control process exited,
code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support:
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
i just swapped the provided file to /etc/named.conf and restarted, thoughts?
My immediate thoughts are:
Ed's named.conf file listed a bunch of files, chances are that yours
have different names and/or filepaths.
Or your files do have formatting errors.