Failed to start Berkeley Internet Name Domain (DNS).

[dbyrd JANO]

I am brand new to CentOS, I am trying to start the BIND Service on our CENTOS 7 AD Server in order to let Windows 10 clients use DNS.

I am getting the following error while trying to start BIND service. Please advise on what steps to take.

[root@DC3 ~]# 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 Tue 2019-02-19 10:37:18 CST; 13min ago
Process: 6831 ExecStartPre=/bin/bash -c if [ ! "$DISABLE_ZONE_CHECKING" == "yes" ]; then /usr/sbin/named-checkconf -z "$NAMEDCONF"; else echo "Checking of zone files is disabled"; fi (code=exited, status=1/FAILURE)

Feb 19 10:37:18 DC3 systemd[1]: Starting Berkeley Internet Name Domain (DNS)...
Feb 19 10:37:18 DC3 bash[6831]: /etc/named.conf:60: open: /usr/local/samba/private/named.conf: file not found
Feb 19 10:37:18 DC3 systemd[1]: named.service: control process exited, code=exited status=1
Feb 19 10:37:18 DC3 systemd[1]: Failed to start Berkeley Internet Name Domain (DNS).
Feb 19 10:37:18 DC3 systemd[1]: Unit named.service entered failed state.
Feb 19 10:37:18 DC3 systemd[1]: named.service failed.

[avij]

/usr/local/samba/private/named.conf: file not found sounds like a fairly good hint to me.

[dbyrd JANO]

@avij
Thanks for responding back to me.
Do you know how I can obtain the named.conf file and copy the named.conf file onto my CENTOS 7 Server?

[avij]

Sorry, but that configuration file is not provided by CentOS. Nothing provided by CentOS uses /usr/local/samba. You would need to figure out why your /etc/named.conf refers to that /usr/local/samba/private/named.conf file.

[dbyrd JANO]

@avij
What is your recommendation for me in order to be able to use CENTOS 7 as a DNS server?

Is there a list of step by step instructions that shows me how to set it up?

[avij]

The /etc/named.conf as shipped by CentOS does not contain a reference to /usr/local/samba/private/named.conf. It is something that you have added yourself.

I don't know what you have done to your system, so it's hard for me to give you a recommendation. Perhaps you should have a look at your /etc/named.conf and edit out the reference to /usr/local/samba/private/named.conf. Maybe it works, maybe it doesn't.

[dbyrd JANO]

Ok I removed the /usr/local/samba/private/named.conf.
I restarted the Service and now the webpages are resolving just fine.

Does the following mean anything to you?

systemctl status named.service
● named.service - Berkeley Internet Name Domain (DNS)
Loaded: loaded (/usr/lib/systemd/system/named.service; enabled; vendor preset: disabled)
Active: active (running) since Wed 2019-02-27 13:35:09 CST; 13min ago
Process: 1003 ExecStart=/usr/sbin/named -u named -c ${NAMEDCONF} $OPTIONS (code=exited, status=0/SUCCESS)
Process: 854 ExecStartPre=/bin/bash -c if [ ! "$DISABLE_ZONE_CHECKING" == "yes" ]; then /usr/sbin/named-checkconf -z "$NAMEDCONF"; else echo "Checking of zone files is disabled"; fi (code=exited, status=0/SUCCESS)
Main PID: 1015 (named)
CGroup: /system.slice/named.service
└─1015 /usr/sbin/named -u named -c /etc/named.conf

Feb 27 13:44:04 DC3 named[1015]: network unreachable resolving 'ns-825.awsdns-39.net/AAAA/IN': 2600:9000:5303:2900::1#53
Feb 27 13:44:04 DC3 named[1015]: network unreachable resolving 'ccg-lenovo.com/A/IN': 2600:9000:5304:7900::1#53
Feb 27 13:45:14 DC3 named[1015]: network unreachable resolving 'tm1.edgedns-tm.info/A/IN': 2603:1061::4#53
Feb 27 13:45:14 DC3 named[1015]: network unreachable resolving 'tm1.edgedns-tm.info/AAAA/IN': 2603:1061::4#53
Feb 27 13:45:14 DC3 named[1015]: network unreachable resolving 'tm1.edgedns-tm.info/A/IN': 2620:1ec:8ec::4#53
Feb 27 13:45:14 DC3 named[1015]: network unreachable resolving 'tm1.edgedns-tm.info/AAAA/IN': 2620:1ec:8ec::4#53
Feb 27 13:45:14 DC3 named[1015]: network unreachable resolving 'tm1.edgedns-tm.info/A/IN': 2a01:111:4000::4#53
Feb 27 13:45:14 DC3 named[1015]: network unreachable resolving 'tm1.edgedns-tm.info/AAAA/IN': 2a01:111:4000::4#53
Feb 27 13:45:14 DC3 named[1015]: network unreachable resolving 'tm1.edgedns-tm.info/A/IN': 2620:1ec:bda::4#53
Feb 27 13:45:14 DC3 named[1015]: network unreachable resolving 'tm1.edgedns-tm.info/AAAA/IN': 2620:1ec:bda::4#53

[dbyrd JANO]

Also, wanted to add that I am using CentOS as an Active Directory Server for my clients as well.

[TrevorH]

I'd say those probably show your ipv6 stack isn't working very well.