Gilbert,

Thank you for your reply. Here are the results of the journalctl - xn command:

-- Logs begin at Wed 2014-11-19 14:28:30 MST, end at Thu 2014-11-20 16:41:02 MST. --
Nov 20 16:41:02 stnicholas.linuxlab.org named-checkconf[18137]: internal/13.8.6.in-addr.arpa/IN: unknown class/type
Nov 20 16:41:02 stnicholas.linuxlab.org named-checkconf[18137]: zone localhost.localdomain/IN: loaded serial 0
Nov 20 16:41:02 stnicholas.linuxlab.org named-checkconf[18137]: zone localhost/IN: loaded serial 0
Nov 20 16:41:02 stnicholas.linuxlab.org named-checkconf[18137]: 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 0
Nov 20 16:41:02 stnicholas.linuxlab.org named-checkconf[18137]: zone 1.0.0.127.in-addr.arpa/IN: loaded serial 0
Nov 20 16:41:02 stnicholas.linuxlab.org named-checkconf[18137]: zone 0.in-addr.arpa/IN: loaded serial 0
Nov 20 16:41:02 stnicholas.linuxlab.org named-checkconf[18137]: zone linuxlab.org.wan/IN: loaded serial 2014071001
Nov 20 16:41:02 stnicholas.linuxlab.org systemd[1]: named.service: control process exited, code=exited status=1
Nov 20 16:41:02 stnicholas.linuxlab.org 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.
Nov 20 16:41:02 stnicholas.linuxlab.org systemd[1]: Unit named.service entered failed state.

The issue is that BIND will not start. I bolded that problematic line. Please let me know what I could do to get BIND up and running. I did do enabling and disabling before, but that doesn't affect the BIND service.

Anthony Radzykewycz

On Thu, Nov 20, 2014 at 1:34 PM, Gilbert T. Gutierrez, Jr. <mailing-lists@phoenixinternet.net> wrote:

Are there any errors in the log? To start it you should run "systemctl start named.service"

To enable startup on boot, "systemctl enable named.service"
To disable startup on boot, "systemctl disable named.service"

Gilbert

On 11/19/2014 10:53 PM, Anthony Radzykewycz wrote:
Hello Everyone,

I am trying to get a DNS/DHCP server up and running using CentOS 7. I have modified the /etc/named.conf file and created the zone files. I attempt to start the named service with 'systemctl start named,' and it fails. Upon investigating 'systemctl status named.service,' it shows that BIND will not start. BIND is installed on the system. I read quite a few forums to no avail. Some were saying that the issue is with the bind-chroot package (which I re-installed), another stated that it was SElinux (I ran 'restorecon /etc/named.conf' 'touch /.autorelabel' 'reboot'). That also did not resolve the issue. Does anyone have an idea as to why BIND will not start?

Anthony Radzykewycz
---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss