Bind from network repo - openSUSE 13.1

Hi,

Bind from network repo dosn’t start by default at openSUE 13.1:


#systemctl start named.service
Job for named.service failed. See 'systemctl status named.service' and 'journalctl -xn' for details.

#systemctl status named.service
named.service - LSB: Domain Name System (DNS) server, named
   Loaded: loaded (/etc/init.d/named)
   Active: failed (Result: exit-code) since sob 2014-03-01 11:26:36 CET; 8s ago
  Process: 4663 ExecStart=/etc/init.d/named start (code=exited, status=1/FAILURE)

mar 01 11:26:36 green named[4708]: adjusted limit on open files from 4096 to 1048576
mar 01 11:26:36 green named[4708]: found 8 CPUs, using 8 worker threads
mar 01 11:26:36 green named[4708]: using 8 UDP listeners per interface
mar 01 11:26:36 green named[4708]: using up to 4096 sockets
mar 01 11:26:36 green named[4708]: loading configuration: failure
mar 01 11:26:36 green named[4708]: exiting (due to fatal error)
mar 01 11:26:36 green named[4663]: Starting name server BIND ..failed
mar 01 11:26:36 green systemd[1]: named.service: control process exited, code=exited status=1
mar 01 11:26:36 green systemd[1]: Failed to start LSB: Domain Name System (DNS) server, named.
mar 01 11:26:36 green systemd[1]: Unit named.service entered failed state.

#journalctl -xn
-- Logs begin at sob 2014-03-01 08:16:34 CET, end at sob 2014-03-01 11:27:56 CET. --
mar 01 11:27:56 green named[4768]: adjusted limit on open files from 4096 to 1048576
mar 01 11:27:56 green named[4768]: found 8 CPUs, using 8 worker threads
mar 01 11:27:56 green named[4768]: using 8 UDP listeners per interface
mar 01 11:27:56 green named[4768]: using up to 4096 sockets
mar 01 11:27:56 green named[4768]: loading configuration: failure
mar 01 11:27:56 green named[4768]: exiting (due to fatal error)
mar 01 11:27:56 green named[4723]: Starting name server BIND ..failed
mar 01 11:27:56 green systemd[1]: named.service: control process exited, code=exited status=1
mar 01 11:27:56 green systemd[1]: Failed to start LSB: Domain Name System (DNS) server, named.
-- Subject: Unit named.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba40df7e9d022f03d
-- 
-- Unit named.service has failed.
-- 
-- The result is failed.
mar 01 11:27:56 green systemd[1]: Unit named.service entered failed state.

Does anyone have any idea?

and is it a good idea to use bind from this repo at a production server?

Well, it cannot read the configuration, I’d say.
Maybe have a look whether there’s a bind/named log file in /var/log that might tell what exactly the problem is.

and is it a good idea to use bind from this repo at a production server?

No idea. But why would you want to do that, and not just use the one included in 13.1?
AFAICS they are the same version anyway at the moment.

The network repo is a development project for Factory (i.e. the next openSUSE version), so might break any time.
If you want a stable version, better stay with the released packages.

The log file says the same, only:

loading configuration: failure

That’s what I thought. I will use the one included in 13.1.
Thanks