Job for named service failed because the control process exited with error code

after i setup dns and try to restart DNS i get this message

Job for named.service failed because the control process exited with error code. See «systemctl status named.service» and «journalctl -xe» for details.

Any solution ?

Logged

after restart click on the status button and then paste that info here

Logged

this is the information.

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 Wed 2017-03-29 11:23:53 EDT; 20s ago
  Process: 889 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=1/FAILURE)

Mar 29 11:23:53 agapechristianchatroom.com bash[889]: zone NS2.AGAPECHRISTIANCHATROOM.COM/IN: loaded serial 2013071600
Mar 29 11:23:53 agapechristianchatroom.com bash[889]: zone agapechristianchatroom.com/IN: NS ‘NS1.AGAPECHRISTIANCHATROOM.COM’ has no address records (A or AAAA)
Mar 29 11:23:53 agapechristianchatroom.com bash[889]: zone agapechristianchatroom.com/IN: NS ‘NS2.AGAPECHRISTIANCHATROOM.COM’ has no address records (A or AAAA)
Mar 29 11:23:53 agapechristianchatroom.com bash[889]: zone agapechristianchatroom.com/IN: not loaded due to errors.
Mar 29 11:23:53 agapechristianchatroom.com bash[889]: _default/agapechristianchatroom.com/IN: bad zone
Mar 29 11:23:53 agapechristianchatroom.com bash[889]: zone whatstruelove.com/IN: loaded serial 2013071600
Mar 29 11:23:53 agapechristianchatroom.com systemd[1]: named.service: control process exited, code=exited status=1
Mar 29 11:23:53 agapechristianchatroom.com systemd[1]: Failed to start Berkeley Internet Name Domain (DNS).
Mar 29 11:23:53 agapechristianchatroom.com systemd[1]: Unit named.service entered failed state.
Mar 29 11:23:53 agapechristianchatroom.com systemd[1]: named.service failed.

Logged

Greetings Friend, error is clear, you must create an A record for those dns

NS1.AGAPECHRISTIANCHATROOM.COM ‘has no address records (A or AAAA)

Logged

do i need to create A records on domain registrar ? because on domain registrar A records is already there and on hosting where centos web panel is installed A records is there.

What shall i do now ?

Can you confirm.

Logged

i figured out problem by deleting nameserver from centos web panel front page right bottom site by clicking on change and retyping nameservers in small letters.

this is a bug in centos web panel, i think caps doesnt works and it doesnt bind dns.

Logged

i figured out problem by deleting nameserver from centos web panel front page right bottom site by clicking on change and retyping nameservers in small letters.

this is a bug in centos web panel, i think caps doesnt works and it doesnt bind dns.

This one solved the problem for me.

Logged

● 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 Sun 2021-05-09 13:11:51 CEST; 5s ago
  Process: 11823 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)

May 09 13:11:51 vmi577947.contaboserver.net bash[11823]: _default/ns1.slmbilisim.net/IN: file not found
May 09 13:11:51 vmi577947.contaboserver.net bash[11823]: zone cosareryapi.com/IN: loaded serial 2021050844
May 09 13:11:51 vmi577947.contaboserver.net bash[11823]: zone ns2.slmyonetim.com/IN: loaded serial 2021050860
May 09 13:11:51 vmi577947.contaboserver.net bash[11823]: zone vmi577947.contaboserver.net/IN: loaded serial 2021050858
May 09 13:11:51 vmi577947.contaboserver.net bash[11823]: zone ns3.slmbilisim.net/IN: loaded serial 2013071600
May 09 13:11:51 vmi577947.contaboserver.net bash[11823]: zone ns4.slmbilisim.net/IN: loaded serial 2013071600
May 09 13:11:51 vmi577947.contaboserver.net systemd[1]: named.service: control process exited, code=exited status=1
May 09 13:11:51 vmi577947.contaboserver.net systemd[1]: Failed to start Berkeley Internet Name Domain (DNS).
May 09 13:11:51 vmi577947.contaboserver.net systemd[1]: Unit named.service entered failed state.
May 09 13:11:51 vmi577947.contaboserver.net systemd[1]: named.service failed.

Logged

After upgraded to SLES 15 SP4 from a previous service pack, named.service will not start and produces the following errors.

# systemctl start named.service
Job for named.service failed because the control process exited with error code.
See "systemctl status named.service" and "journalctl -xeu named.service" for details.
# journalctl -xeu named.service
...
Oct 20 12:01:55 host15sp4 named[4111]: isc_stdio_open '/var/log/named_querylog' failed: permission denied
Oct 20 12:01:55 host15sp4 named[4111]: configuring logging: permission denied
Oct 20 12:01:55 host15sp4 named[4111]: loading configuration: permission denied
Oct 20 12:01:55 host15sp4 named[4111]: exiting (due to fatal error)
Oct 20 12:01:55 host15sp4 systemd[1]: named.service: Control process exited, code=exited, status=1/FAILURE
...

Query logging for bind is enabled and configured to log to a file in /var/log/ by having a configuration similar to the following in the file /etc/named.conf.

logging {
        # Log queries to a file limited to a size of 100 MB.
        channel query_logging {
                file "/var/log/named_querylog"
                        versions 3 size 100M;
                print-time yes;                 // timestamp log entries
        };
        category queries {
                query_logging;
        };

The following line in /etc/sysconfig/named is currently present, or was present when bind was run in the previous service pack.

NAMED_RUN_CHROOTED="yes"

Edit the file /etc/named.conf by changing

# Log queries to a file limited to a size of 100 MB.
        channel query_logging {
                file "/var/log/named_querylog"

to

# Log queries to a file limited to a size of 100 MB.
        channel query_logging {
                file "/var/lib/named/log/named_querylog"

This will cause logs to be written to /var/lib/named/log/named_querylog instead of the previous location, /var/lib/named/var/log/named_querylog.

In previous service packs, the default configuration ran bind in a chroot jail in /var/lib/named. Changes were made for SLES 15 SP4 with regards to this chroot setup.

The logging path from /etc/named.conf used to be evaluated relative to this chroot location, but is now evaluated relative to the system root.

The default configuration on previous service packs set /var/log/named_querylog as the destination for logs. In the previous chroot environment, this caused logs to be written to /var/lib/named/var/log/named_querylog. With the SLES 15 SP4 changes to bind, this same setting causes logs to be written to /var/log/named_querylog.

Logs are written by the user named. This user does not have permission to write to this new location by default which creates the errors observed.