Anthony,

If the chrooted bind on CentOS 7 is anything like the one on RHEL 6, all the files should be relative to the /var/named/chroot directory.  Which would put "/etc/named.conf" at /var/named/chroot/etc/named.conf, /var/named would be /var/named/chroot/var/named, and so on.  

Or you could remove the bind-chroot package and see if bind starts in your current configuration.

TJ


---- Anthony Radzykewycz <anthony.radzykewycz@gatewaycc.edu> 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