BIND named.service won't start ...

jjb2016 · 2019-12-12 22:36:53

Hi all,

Just recently (not sure exactly when) something has gone wrong with the named.service running on my home server. When I try to start the service I get ...

[justin@IXTREME ~]$ sudo systemctl start named.service
[justin@IXTREME ~]$ sudo systemctl status named.service
● named.service - Internet domain name server
     Loaded: loaded (/usr/lib/systemd/system/named.service; enabled; vendor preset: disabled)
     Active: failed (Result: exit-code) since Thu 2019-12-12 22:25:53 GMT; 1s ago
    Process: 167819 ExecStart=/usr/bin/named -f -u named (code=exited, status=1/FAILURE)
   Main PID: 167819 (code=exited, status=1/FAILURE)

Dec 12 22:25:53 IXTREME named[167819]: listening on IPv4 interface lo, 127.0.0.1#53
Dec 12 22:25:53 IXTREME named[167819]: unable to set effective uid to 0: Operation not permitted
Dec 12 22:25:53 IXTREME named[167819]: generating session key for dynamic DNS
Dec 12 22:25:53 IXTREME named[167819]: unable to set effective uid to 0: Operation not permitted
Dec 12 22:25:53 IXTREME named[167819]: sizing zone task pool based on 6 zones
Dec 12 22:25:53 IXTREME named[167819]: could not configure root hints from 'root.hint': file not found
Dec 12 22:25:53 IXTREME named[167819]: loading configuration: file not found
Dec 12 22:25:53 IXTREME named[167819]: exiting (due to fatal error)
Dec 12 22:25:53 IXTREME systemd[1]: named.service: Main process exited, code=exited, status=1/FAILURE
Dec 12 22:25:53 IXTREME systemd[1]: named.service: Failed with result 'exit-code'.

and the output from journalctl ...

[justin@IXTREME ~]$ sudo journalctl -n 30 -u named
[sudo] password for justin: 
-- Logs begin at Wed 2019-12-11 03:57:20 GMT, end at Thu 2019-12-12 22:32:57 GMT. --
Dec 12 22:25:53 IXTREME named[167819]: compiled with libjson-c version: 0.13.1
Dec 12 22:25:53 IXTREME named[167819]: linked to libjson-c version: 0.13.1
Dec 12 22:25:53 IXTREME named[167819]: compiled with zlib version: 1.2.11
Dec 12 22:25:53 IXTREME named[167819]: linked to zlib version: 1.2.11
Dec 12 22:25:53 IXTREME named[167819]: ----------------------------------------------------
Dec 12 22:25:53 IXTREME named[167819]: BIND 9 is maintained by Internet Systems Consortium,
Dec 12 22:25:53 IXTREME named[167819]: Inc. (ISC), a non-profit 501(c)(3) public-benefit
Dec 12 22:25:53 IXTREME named[167819]: corporation.  Support and training for BIND 9 are
Dec 12 22:25:53 IXTREME named[167819]: available at https://www.isc.org/support
Dec 12 22:25:53 IXTREME named[167819]: ----------------------------------------------------
Dec 12 22:25:53 IXTREME named[167819]: adjusted limit on open files from 524288 to 1048576
Dec 12 22:25:53 IXTREME named[167819]: found 8 CPUs, using 8 worker threads
Dec 12 22:25:53 IXTREME named[167819]: using 8 UDP listeners per interface
Dec 12 22:25:53 IXTREME named[167819]: using up to 4096 sockets
Dec 12 22:25:53 IXTREME named[167819]: loading configuration from '/etc/named.conf'
Dec 12 22:25:53 IXTREME named[167819]: reading built-in trust anchors from file '/etc/bind.keys'
Dec 12 22:25:53 IXTREME named[167819]: looking for GeoIP2 databases in '/usr/share/GeoIP'
Dec 12 22:25:53 IXTREME named[167819]: using default UDP/IPv4 port range: [32768, 60999]
Dec 12 22:25:53 IXTREME named[167819]: using default UDP/IPv6 port range: [32768, 60999]
Dec 12 22:25:53 IXTREME named[167819]: listening on IPv6 interfaces, port 53
Dec 12 22:25:53 IXTREME named[167819]: listening on IPv4 interface lo, 127.0.0.1#53
Dec 12 22:25:53 IXTREME named[167819]: unable to set effective uid to 0: Operation not permitted
Dec 12 22:25:53 IXTREME named[167819]: generating session key for dynamic DNS
Dec 12 22:25:53 IXTREME named[167819]: unable to set effective uid to 0: Operation not permitted
Dec 12 22:25:53 IXTREME named[167819]: sizing zone task pool based on 6 zones
Dec 12 22:25:53 IXTREME named[167819]: could not configure root hints from 'root.hint': file not found
Dec 12 22:25:53 IXTREME named[167819]: loading configuration: file not found
Dec 12 22:25:53 IXTREME named[167819]: exiting (due to fatal error)
Dec 12 22:25:53 IXTREME systemd[1]: named.service: Main process exited, code=exited, status=1/FAILURE
Dec 12 22:25:53 IXTREME systemd[1]: named.service: Failed with result 'exit-code'.

So, it mentions "could not configure root hints ..."
and "loading configuration file: file not found"

But, I'm not sure what the root.hint file is or where it should be, and I'm not sure what configuration file could not be found. The main named.conf file was found by the looks of it.

I'm at a loss ... Any ideas?

Zod · 2019-12-12 22:42:28

http://archlinux.2023198.n4.nabble.com/ … 24815.html

?

jjb2016 · 2019-12-13 13:18:11

Thanks Zod. I can confirm that removing the "." zone from my /etc/named.conf file solved the issue. Back up and running again.

Arch Linux

#1 2019-12-12 22:36:53

BIND named.service won't start ...

#2 2019-12-12 22:42:28

Re: BIND named.service won't start ...

#3 2019-12-13 13:18:11

Re: BIND named.service won't start ...

Board footer