Anthony,
I looked a little further...
In Centos7 (without chroot, I have not looked at the chroot version),
the named.conf file is in /etc and not /etc/named.
The start up file is /usr/lib/systemd/system/named.service which will
show you what is being called and from where.
I wish I was more help, but I have done very little with CentOS7. All my
DNS servers are running on CentOS5 and I need to think about replacing
them, which I would do on CentOS7.
Gilbert
On 11/21/2014 12:02 PM, Anthony Radzykewycz wrote:
Oh ok. Thank you!! I will start from the beginning again and work on
it until I break it or it works. I guess I am lucky in the respect
that I am doing all of this from scratch. Thank you for the info and I
will let you know if my initial install doesn't start BIND still.
On Fri, Nov 21, 2014 at 12:01 PM, Anthony Radzykewycz
<[email protected]> wrote:
Ok. I will also install a VM to try to recreate it. I can attempt to
start the named service right after my install to see if I screwed
something up. Thanks for your help. :-)
On Fri, Nov 21, 2014 at 11:38 AM, Gilbert T. Gutierrez, Jr.
<[email protected]> wrote:
Anthony,
I looked at your responses to TJ, Lisa, and myself. What you provided does
not tell me what the issue is. Have you tried starting from scratch?
Uninstall bind, delete leftover configuration files found in /var/named and
/etc/named, reinstall, and try to start the base configuration with no
modifications? I am going to create a test environment here and see if I can
get the same issue to appear.
Gilbert
On 11/20/2014 10:00 PM, [email protected] 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 <[email protected]> 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 - [email protected]
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss
---------------------------------------------------
PLUG-discuss mailing list - [email protected]
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss
---------------------------------------------------
PLUG-discuss mailing list - [email protected]
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss
---------------------------------------------------
PLUG-discuss mailing list - [email protected]
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss
