erro ao executar o comando: systemctl restart named, no CentOS [RESOLVIDO]

Ricardomendes24
(usa CentOS)

Enviado em 20/02/2019 - 15:39h

o erro é esse: Job for named.service failed because the control process exited with error code. See "systemctl status named.service" and "journalctl -xe" for details.

sim já desativei o firewalld e selinux

já revisei todo o código do named.conf.

vou mandar o resultado dos testes e os erros:

******************* firewalld desativado e selinux tambem ***********************

[root@servidorCCRei samba-4.8.3]# systemctl restart named

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

[root@servidorCCRei samba-4.8.3]# systemctl status firewalld

● firewalld.service - firewalld - dynamic firewall daemon

Loaded: loaded (/usr/lib/systemd/system/firewalld.service; disabled; vendor preset: enabled)

Active: inactive (dead)

Docs: man:firewalld(1)

Fev 20 10:05:39 servidorCCRei systemd[1]: Starting firewalld - dynamic firewall daemon...

Fev 20 10:05:43 servidorCCRei systemd[1]: Started firewalld - dynamic firewall daemon.

Fev 20 10:55:51 servidorCCRei systemd[1]: Stopping firewalld - dynamic firewall daemon...

Fev 20 10:55:52 servidorCCRei systemd[1]: Stopped firewalld - dynamic firewall daemon.

[root@servidorCCRei samba-4.8.3]# nano /etc/selinux/config

[root@servidorCCRei samba-4.8.3]# setenforce 0

[root@servidorCCRei samba-4.8.3]# getenforce

Permissive

[root@servidorCCRei samba-4.8.3]# systemctl restart named

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

******************************* este é o arquivo named.conf ************************************************************************

[root@servidorCCRei samba-4.8.3]# nano /etc/named.conf

GNU nano 2.3.1 Arquivo: /etc/named.conf Modificado

// // named.conf // // Provided by Red Hat bind package to configure the ISC BIND named(8) DNS // server as a caching only nameserver (as a localhost

DNS resolver only). // // See /usr/share/doc/bind*/sample/ for example named configuration files. // // See the BIND Administrator's Reference Manual

(ARM) for details about the // configuration located in /usr/share/doc/bind-{version}/Bv9ARM.html

options {

listen-on port 53 { 127.0.0.1;any; };

tkey-gssapi-keytab "/var/lib/samba/bind-dns/dns.keytab";

listen-on-v6 port 53 { ::1; };

directory "/var/named";

dump-file "/var/named/data/cache_dump.db";

statistics-file "/var/named/data/named_stats.txt";

memstatistics-file "/var/named/data/named_mem_stats.txt";

recursing-file "/var/named/data/named.recursing";

secroots-file "/var/named/data/named.secroots";

allow-query { localhost;any; };

/*

- If you are building an AUTHORITATIVE DNS server, do NOT enable recursion.

- If you are building a RECURSIVE (caching) DNS server, you need to enable

recursion.

- If your recursive DNS server has a public IP address, you MUST enable access

control to limit queries to your legitimate users. Failing to do so will

cause your server to become part of large scale DNS amplification

attacks. Implementing BCP38 within your network would greatly

reduce such attack surface

*/

recursion yes;

dnssec-enable yes;

dnssec-validation yes;

/* Path to ISC DLV key */

bindkeys-file "/etc/named.iscdlv.key";

managed-keys-directory "/var/named/dynamic";

pid-file "/run/named/named.pid";

session-keyfile "/run/named/session.key";

};

[ É possível DesJustificar! ]

^G Ajuda ^O Gravar ^R Ler o Arq ^Y Pág Anter ^K Recort Txt ^C Pos Atual

^X Sair ^J Justificar ^W Onde está? ^V Próx Pág ^U DesJustifi ^T Para Spell

************************** ao executar o comando pra ver os status sai assim *******************************************************

[root@servidorCCRei samba-4.8.3]# systemctl restart named.service

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

[root@servidorCCRei samba-4.8.3]# 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 Qua 2019-02-20 15:09:44 -03; 26s ago

Process: 8637 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)

Fev 20 15:09:44 servidorCCRei systemd[1]: Starting Berkeley Internet Name Domain (DNS)...

Fev 20 15:09:44 servidorCCRei bash[8637]: /etc/named.conf:2: unknown option 'DNS'

Fev 20 15:09:44 servidorCCRei systemd[1]: named.service: control process exited, code=exited status=1

Fev 20 15:09:44 servidorCCRei systemd[1]: Failed to start Berkeley Internet Name Domain (DNS).

Fev 20 15:09:44 servidorCCRei systemd[1]: Unit named.service entered failed state.

Fev 20 15:09:44 servidorCCRei systemd[1]: named.service failed.

[root@servidorCCRei samba-4.8.3]#

**************************************** esse é o resultado do journalctl -xe ***********************************************************

[root@servidorCCRei samba-4.8.3]# journalctl -xe

-- Subject: Unidade NetworkManager-dispatcher.service concluiu a inicialização

-- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

--

-- A unidade NetworkManager-dispatcher.service concluiu a inicialização.

--

-- The start-up result is done.

Fev 20 15:05:01 servidorCCRei nm-dispatcher[8609]: req:1 'dhcp4-change' [enp0s8]: new request (2 scripts)

Fev 20 15:05:01 servidorCCRei nm-dispatcher[8609]: req:1 'dhcp4-change' [enp0s8]: start running ordered scripts...

Fev 20 15:09:44 servidorCCRei polkitd[2627]: Registered Authentication Agent for unix-process:8628:1826553 (system bus name :1.174 [/usr/bin/pkttyagent --not

Fev 20 15:09:44 servidorCCRei systemd[1]: Starting Generate rndc key for BIND (DNS)...

-- Subject: Unidade named-setup-rndc.service sendo iniciado

-- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

--

-- A unidade named-setup-rndc.service está sendo iniciada.

Fev 20 15:09:44 servidorCCRei systemd[1]: Started Generate rndc key for BIND (DNS).

-- Subject: Unidade named-setup-rndc.service concluiu a inicialização

-- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

--

-- A unidade named-setup-rndc.service concluiu a inicialização.

--

-- The start-up result is done.

Fev 20 15:09:44 servidorCCRei systemd[1]: Starting Berkeley Internet Name Domain (DNS)...

-- Subject: Unidade named.service sendo iniciado

-- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

--

-- A unidade named.service está sendo iniciada.

Fev 20 15:09:44 servidorCCRei bash[8637]: /etc/named.conf:2: unknown option 'DNS'

Fev 20 15:09:44 servidorCCRei systemd[1]: named.service: control process exited, code=exited status=1

Fev 20 15:09:44 servidorCCRei systemd[1]: Failed to start Berkeley Internet Name Domain (DNS).

-- Subject: A unidade named.service falhou

-- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

--

-- A unidade named.service falhou.

--

-- O resultado é failed.

Fev 20 15:09:44 servidorCCRei systemd[1]: Unit named.service entered failed state.

Fev 20 15:09:44 servidorCCRei systemd[1]: named.service failed.

Fev 20 15:09:44 servidorCCRei polkitd[2627]: Unregistered Authentication Agent for unix-process:8628:1826553 (system bus name :1.174, object path /org/freede

lines 1474-1516/1516 (END)

No final de tudo nao encontro onde danado ta o erro ta tudo certinho, se alguém puder me ajudar ficarei agradecido.

renato_pacheco
(usa Debian)

Enviado em 21/02/2019 - 08:39h

Olhe aqui o erro:

Fev 20 15:09:44 servidorCCRei bash[8637]: /etc/named.conf:2: unknown option 'DNS'

 

Retire esses comentários lá do named.conf, pois comentários em arquivos bind não são com barras duplas, mas com ponto-e-vírgula.

--
http://br.linkedin.com/in/renatocarneirop
http://www.facebook.com/renatocarneirop

"Não acredite no que eu digo, pois é a minha experiência e não a sua. Experimente, indague e busque." - Osho Rajneesh

Ricardomendes24
(usa CentOS)

Enviado em 21/02/2019 - 11:37h

muito obrigado, é tanta informação na tela que não estava encontrando onde ele mostrava o erro obg mesmo.

renato_pacheco
(usa Debian)

Enviado em 22/02/2019 - 08:49h

Acontece nas melhores famílias. Os logs são seus melhores amigos, cara...

--
http://br.linkedin.com/in/renatocarneirop
http://www.facebook.com/renatocarneirop

"Não acredite no que eu digo, pois é a minha experiência e não a sua. Experimente, indague e busque." - Osho Rajneesh