Bind failing to start on new 9.9.4 server
Robert Moskowitz
rgm at htt-consult.com
Thu Feb 9 14:28:24 UTC 2017
I am migrating to Centos7 from Centos6. Going from Bind 9.8.2 to 9.9.4,
I am building this on a new server. I currently do not have DNSSEC
enabled, and not enabling it for the initial migration work.
I have looked over changes in named.conf and believe I have made the
necessary changes. My named.conf is loading as are the zone files.
This is what 'systemctl -l status named' shows:
● 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 Thu 2017-02-09 09:08:25
EST; 14min ago
Process: 1851 ExecStart=/usr/sbin/named -u named $OPTIONS
(code=exited, status=1/FAILURE)
Process: 1847 ExecStartPre=/bin/bash -c if [ !
"$DISABLE_ZONE_CHECKING" == "yes" ]; then /usr/sbin/named-checkconf -z
/etc/named.conf; else echo "Checking of zone files is disabled"; fi
(code=exited, status=0/SUCCESS)
Feb 09 09:08:25 onlo.htt-consult.com named[1855]: automatic empty zone:
view internal: 74.100.IN-ADDR.ARPA
Feb 09 09:08:25 onlo.htt-consult.com named[1855]: automatic empty zone:
view internal: 75.100.IN-ADDR.ARPA
Feb 09 09:08:25 onlo.htt-consult.com named[1855]: automatic empty zone:
view internal: 76.100.IN-ADDR.ARPA
Feb 09 09:08:25 onlo.htt-consult.com named[1855]: automatic empty zone:
view internal: 77.100.IN-ADDR.ARPA
Feb 09 09:08:25 onlo.htt-consult.com named[1855]: automatic empty zone:
view internal: 78.100.IN-ADDR.ARPA
Feb 09 09:08:25 onlo.htt-consult.com named[1855]: automatic empty zone:
view internal: 79.100.IN-ADDR.ARPA
Feb 09 09:08:25 onlo.htt-consult.com systemd[1]: named.service: control
process exited, code=exited status=1
Feb 09 09:08:25 onlo.htt-consult.com systemd[1]: Failed to start
Berkeley Internet Name Domain (DNS).
Feb 09 09:08:25 onlo.htt-consult.com systemd[1]: Unit named.service
entered failed state.
Feb 09 09:08:25 onlo.htt-consult.com systemd[1]: named.service failed.
Not very informative with all those auto empty zone messages. Is there
a way to suppress those messages, or is this part of the problem?
I worked at viewing /var/log/messages, digging through all those auto
empty zone messages and found the following:
Feb 9 09:08:25 onlo named[1855]: automatic empty zone: view internal:
101.100.I
N-ADDR.ARPA
Feb 9 09:08:25 onlo named[1855]: automatic empty zone: view internal:
102.100.I
N-ADDR.ARPA
Feb 9 09:08:25 onlo named[1855]: automatic empty zone: view internal:
103.100.I
N-ADDR.ARPA
Feb 9 09:08:25 onlo named[1855]: automatic empty zone: view internal:
104.100.I
N-ADDR.ARPA
Feb 9 09:08:25 onlo named[1855]: automatic empty zone: view internal:
105.100.I
N-ADDR.ARPA
Feb 9 09:08:25 onlo named[1855]: automatic empty zone: view internal:
106.100.I
N-ADDR.ARPA
Feb 9 09:08:25 onlo named[1855]: automatic empty zone: view internal:
107.100.I
N-ADDR.ARPA
Feb 9 09:08:25 onlo named[1855]: automatic empty zone: view internal:
108.100.I
N-ADDR.ARPA
Feb 9 09:08:25 onlo named[1855]: automatic empty zone: view internal:
109.100.I
N-ADDR.ARPA
Feb 9 09:08:25 onlo systemd: named.service: control process exited,
code=exited
status=1
Feb 9 09:08:25 onlo named[1855]: automatic empty zone: view internal:
110.100.I
N-ADDR.ARPA
Feb 9 09:08:25 onlo systemd: Failed to start Berkeley Internet Name
Domain (DNS
).
Feb 9 09:08:25 onlo named[1855]: automatic empty zone: view internal:
111.100.I
N-ADDR.ARPA
Feb 9 09:08:25 onlo systemd: Unit named.service entered failed state.
Feb 9 09:08:25 onlo named[1855]: automatic empty zone: view internal:
112.100.I
N-ADDR.ARPA
Feb 9 09:08:25 onlo systemd: named.service failed.
Feb 9 09:08:25 onlo named[1855]: automatic empty zone: view internal:
113.100.I
N-ADDR.ARPA
Feb 9 09:08:25 onlo named[1855]: automatic empty zone: view internal:
114.100.I
N-ADDR.ARPA
Feb 9 09:08:25 onlo named[1855]: automatic empty zone: view internal:
115.100.I
N-ADDR.ARPA
Feb 9 09:08:25 onlo named[1855]: automatic empty zone: view internal:
116.100.I
N-ADDR.ARPA
Feb 9 09:08:25 onlo named[1855]: automatic empty zone: view internal:
117.100.I
named enters failed state and no reason why is given. Perhaps it is the
number of empty zones generated?
Thank you for your help on this.
More information about the bind-users
mailing list