TJ,
I just moved the /etc/named.conf file and my zone files to where
you specified and still no results. I also tried to remove the
bind-chroot package and start the named service, and that still didn't
start BIND. Here is the output of what I tried just now.
[root@stnicholas named]# ls /var/named/chroot/etc/
localtime named named.conf pki
[root@stnicholas named]# ls /var/named/chroot/var/named/
13.8.6.db linuxlab.org.lan named.ca named.loopback
80.0.16.172.db linuxlab.org.wan named.localhost
[root@stnicholas named]# systemctl start named.service
Job for named.service failed. See 'systemctl status named.service' and
'journalctl -xn' for details.
[root@stnicholas named]# systemctl status named.service
named.service - Berkeley Internet Name Domain (DNS)
Loaded: loaded (/usr/lib/systemd/system/named.service; disabled)
Active: failed (Result: exit-code) since Fri 2014-11-21 08:29:42 MST; 8s ago
Process: 29506 ExecStartPre=/usr/sbin/named-checkconf -z
/etc/named.conf (code=exited, status=1/FAILURE)
Nov 21 08:29:42 stnicholas.linuxlab.org named-checkconf[29506]: internal/13.8...
Nov 21 08:29:42 stnicholas.linuxlab.org named-checkconf[29506]: zone localhos...
Nov 21 08:29:42 stnicholas.linuxlab.org named-checkconf[29506]: zone localhos...
Nov 21 08:29:42 stnicholas.linuxlab.org named-checkconf[29506]: zone 1.0.0.0....
Nov 21 08:29:42 stnicholas.linuxlab.org named-checkconf[29506]: zone 1.0.0.12...
Nov 21 08:29:42 stnicholas.linuxlab.org named-checkconf[29506]: zone 0.in-add...
Nov 21 08:29:42 stnicholas.linuxlab.org named-checkconf[29506]: zone linuxlab...
Nov 21 08:29:42 stnicholas.linuxlab.org systemd[1]: named.service: control pr...
Nov 21 08:29:42 stnicholas.linuxlab.org systemd[1]: Failed to start Berkeley ...
Nov 21 08:29:42 stnicholas.linuxlab.org systemd[1]: Unit named.service entere...
Hint: Some lines were ellipsized, use -l to show in full.
On Thu, Nov 20, 2014 at 10:00 PM, <
tjones136@cox.net> wrote:
> 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
(text/plain)