Failed to start BIND

Submitted by neopraxis on Thu, 02/18/2016 - 13:50

I have this issue since install, but since I was using the registrars dns I didn't prioritise this, but now I am increasingly feeling like this is having a greater impact on my system as a whole. Ideally I would prefer to run my nameservers on my server.

Failed to start BIND : Redirecting to /bin/systemctl start named.service Job for named.service failed because the control process exited with error code. See "systemctl status named.service" and "journalctl -xe" for details.

Status: 
Active

Comments

Submitted by andreychek on Thu, 02/18/2016 - 14:02

Howdy -- what error(s) are you seeing in the logs, and by running the mentioned commands, when that occurs?

Submitted by neopraxis on Thu, 02/18/2016 - 15:22

Hi,

# 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 Thu 2016-02-18 21:11:15 GMT; 23s ago
  Process: 24218 ExecStartPre=/bin/bash -c if [ ! "$DISABLE_ZONE_CHECKING" == "yes" ]; then /usr/sbin/named-checkconf -z /etc/named.conf; else echo "Checking of zone files is disabled"; fi (code=exited, status=1/FAILURE)

Feb 18 21:11:15 ns338867.ip-178-33-227.eu bash[24218]: zone montie.org/IN: not loaded due to errors.
Feb 18 21:11:15 ns338867.ip-178-33-227.eu bash[24218]: _default/montie.org/IN: bad zone
Feb 18 21:11:15 ns338867.ip-178-33-227.eu bash[24218]: zone jadeking.co.uk/IN: loaded serial 2016021501
Feb 18 21:11:15 ns338867.ip-178-33-227.eu bash[24218]: zone zavrazos.com/IN: loaded serial 2016021501
Feb 18 21:11:15 ns338867.ip-178-33-227.eu bash[24218]: zone test101.com/IN: loaded serial 2016021502
Feb 18 21:11:15 ns338867.ip-178-33-227.eu bash[24218]: zone test101.webpurity.net/IN: loaded serial 2016021501
Feb 18 21:11:15 ns338867.ip-178-33-227.eu systemd[1]: named.service: control process exited, code=exited status=1
Feb 18 21:11:15 ns338867.ip-178-33-227.eu systemd[1]: Failed to start Berkeley Internet Name Domain (DNS).
Feb 18 21:11:15 ns338867.ip-178-33-227.eu systemd[1]: Unit named.service entered failed state.
Feb 18 21:11:15 ns338867.ip-178-33-227.eu systemd[1]: named.service failed. Feb 18 21:11:15 ns338867.ip-178-33-227.eu systemd[1]: Starting Generate rndc key for BIND (DNS)...
-- Subject: Unit named-setup-rndc.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit named-setup-rndc.service has begun starting up.
Feb 18 21:11:15 ns338867.ip-178-33-227.eu systemd[1]: Started Generate rndc key for BIND (DNS).
-- Subject: Unit named-setup-rndc.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit named-setup-rndc.service has finished starting up.
--
-- The start-up result is done.
Feb 18 21:11:15 ns338867.ip-178-33-227.eu systemd[1]: Starting Berkeley Internet Name Domain (DNS)...
-- Subject: Unit named.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit named.service has begun starting up.
Feb 18 21:11:15 ns338867.ip-178-33-227.eu bash[24218]: zone localhost.localdomain/IN: loaded serial 4
Feb 18 21:11:15 ns338867.ip-178-33-227.eu bash[24218]: zone localhost/IN: loaded serial 4
Feb 18 21:11:15 ns338867.ip-178-33-227.eu bash[24218]: 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: loaded serial 4
Feb 18 21:11:15 ns338867.ip-178-33-227.eu bash[24218]: zone 1.0.0.127.in-addr.arpa/IN: loaded serial 4
Feb 18 21:11:15 ns338867.ip-178-33-227.eu bash[24218]: zone 0.in-addr.arpa/IN: loaded serial 2
Feb 18 21:11:15 ns338867.ip-178-33-227.eu bash[24218]: zone webpurity.net/IN: has no NS records
Feb 18 21:11:15 ns338867.ip-178-33-227.eu bash[24218]: zone webpurity.net/IN: not loaded due to errors.
Feb 18 21:11:15 ns338867.ip-178-33-227.eu bash[24218]: _default/webpurity.net/IN: bad zone
Feb 18 21:11:15 ns338867.ip-178-33-227.eu bash[24218]: zone neopraxis.co.uk/IN: loaded serial 2016020202
Feb 18 21:11:15 ns338867.ip-178-33-227.eu bash[24218]: zone zookeeperinc.co.uk/IN: loaded serial 2016020202
Feb 18 21:11:15 ns338867.ip-178-33-227.eu bash[24218]: zone ircarey.co.uk/IN: has no NS records
Feb 18 21:11:15 ns338867.ip-178-33-227.eu bash[24218]: zone ircarey.co.uk/IN: not loaded due to errors.
Feb 18 21:11:15 ns338867.ip-178-33-227.eu bash[24218]: _default/ircarey.co.uk/IN: bad zone
Feb 18 21:11:15 ns338867.ip-178-33-227.eu bash[24218]: zone montie.org/IN: has no NS records
Feb 18 21:11:15 ns338867.ip-178-33-227.eu bash[24218]: zone montie.org/IN: not loaded due to errors.
Feb 18 21:11:15 ns338867.ip-178-33-227.eu bash[24218]: _default/montie.org/IN: bad zone
Feb 18 21:11:15 ns338867.ip-178-33-227.eu bash[24218]: zone jadeking.co.uk/IN: loaded serial 2016021501
Feb 18 21:11:15 ns338867.ip-178-33-227.eu bash[24218]: zone zavrazos.com/IN: loaded serial 2016021501
Feb 18 21:11:15 ns338867.ip-178-33-227.eu bash[24218]: zone test101.com/IN: loaded serial 2016021502
Feb 18 21:11:15 ns338867.ip-178-33-227.eu bash[24218]: zone test101.webpurity.net/IN: loaded serial 2016021501
Feb 18 21:11:15 ns338867.ip-178-33-227.eu systemd[1]: named.service: control process exited, code=exited status=1
Feb 18 21:11:15 ns338867.ip-178-33-227.eu systemd[1]: Failed to start Berkeley Internet Name Domain (DNS).
-- Subject: Unit named.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit named.service has failed.
--
-- The result is failed.
Feb 18 21:11:15 ns338867.ip-178-33-227.eu systemd[1]: Unit named.service entered failed state.
Feb 18 21:11:15 ns338867.ip-178-33-227.eu systemd[1]: named.service failed.

Submitted by andreychek on Thu, 02/18/2016 - 15:32

Ah, it looks like you're receiving errors about not having any "NS" records in a few of your domains. That includes montie.org, ircarey.co.uk, and webpurity.net.

Those should normally be added by default though.

What you may want to do is look at another one of your domains that has NS records added, and copy those back into the DNS records for the above domains. You can view/edit the DNS records in Server Configuration -> DNS Records.

Submitted by neopraxis on Thu, 02/18/2016 - 23:14

Thanks, this is where I think I'm getting confused with the advice I got from my registrar, Namecheap, they said not to have any NS records here, but I may be at fault here.

I want webpurity.net to be used as the primary domain for my dedicated server (hosted at OVH), I want this server to also be ns3.webpurity.net, then I would like to use OVH's Secondary DNS (sdns2.ovh.net) as ns2.webpurity.net if possible and finally a VPS as ns1.webpurity.net. Does this sound reasonable or advisable?

Do I then just add A records (or is it NS records, or both!?) ns1, ns2, ns3.webpurity.net to each domain?

Thanks

Submitted by andreychek on Thu, 02/18/2016 - 18:13

Every DNS zone needs to have "NS" records that say what the nameserver records are for that domain.

Now, whether those point to your server, or a remote service, depends on your setup.

I'm not familiar with using OVH as a secondary DNS provider, though based on their setup that can work.

In general, you'd just want to make sure that you have an "NS" record for each name that's listed as a "nameserver" for the domain at your registrar. There would also need to be a corresponding DNS 'A' record for that name.

Does that answer your question? And does it make sense?

Submitted by neopraxis on Thu, 02/18/2016 - 18:55

So, to clarify, I register each "nameserver" (name and ip) at the registrar and then create a corresponding pair of "NS" and "A" records (glue records) on each server or service?

Pardon my ignorance, but this has got me all turned around.

Submitted by neopraxis on Thu, 02/18/2016 - 20:05

I created NS records in each zone on my server and have been able to start BIND, do I also need to add matching A records here to have 'glue records'?