named dns server not start

[kablakar]

today unexpectedly the named dns server not start never, when try to start show error :

if send this command :

Code: Select all

service named status

show this error:

Code: Select all

rndc: connect failed: 127.0.0.1#953: connection refused

if try to start with this command :

Code: Select all

# service named start

show this ( the "++++++" is my domain"):

Code: Select all

service named start
Avvio di named:
Error in named configuration:
zone default.domain/IN: loaded serial 2015052901
zone +++++++++++/IN: has no NS records
zone ++++++++++++/IN: not loaded due to errors.
_default/+++++++++++++/IN: bad zone
zone ++++++++/IN: has no NS records
zone +++++++++++/IN: not loaded due to errors.
_default/++++++++++++/IN: bad zone
zone ++++++++++++++++/IN: has no NS records
zone +++++++++++++++/IN: not loaded due to errors.
_default/+++++++++++/IN: bad zone
zone ++++++++++++++++++/IN: has no NS records
zone ++++++++++++++++++/IN: not loaded due to errors.
_default/+++++++++++++++++++/IN: bad zone
zone ++++++++++++++++++/IN: has no NS records
zone ++++++++++++++++/IN: not loaded due to errors.
_default/++++++++++++++/IN: bad zone
zone ++++++++++++++/IN: loaded serial 2015052901
zone +++++++++++++++/IN: loaded serial 2015052901
zone ++++++++++++/IN: loaded serial 2015052901
                                                           [FALLITO]

how solve ?

[skurudo]

chown root:named /etc/rndc.key
chmod 640 /etc/rndc.key

service named restart

[zorrobyte]

Same issue on CentOS 6.6 fresh install.

Installer complains about bind-9 already being installed, going to manually remove from fresh install and try installing VestaCP again

[skurudo]

Same issue on CentOS 6.6 fresh install. Installer complains about bind-9 already being installed, going to manually remove from fresh install and try installing VestaCP again

Nope, this not the same issue. Your may thank your hosting provider for not clean OS from template. It's recommended - install on clean OS withouts other software, all needed soft VestaCP install from repo.

[joem]

Same issue on CentOS 6.6 fresh install.

Installer complains about bind-9 already being installed, going to manually remove from fresh install and try installing VestaCP again

I find this works best when installing Vesta on CentOS

Code: Select all

  yum remove httpd* bind* -y
  yum clean all
  curl -O http://vestacp.com/pub/vst-install.sh
  bash vst-install.sh

[EbertonMoraes]

Hello, i have exactly the same problem of the topic... Exactly same errors.

Tryied change permissions:

chown root:named /etc/rndc.key
chmod 640 /etc/rndc.key

service named restart

But not works, still having problem... Can help me with that?

[fwddev]

I'm having the same problem after an auto update that took place over the weekend.
Looks like I'm on version 0.9.8 release 17 for vesta, vesta-php and vesta-nginx.

I made sure the permissions were the same ad mentioned earlier and have rebooted with no dice.

How do I get the Named Service up and Running?

# status named.service
Redirecting to /bin/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 Mon 2017-03-27 15:40:03 EDT; 34min ago
Process: 9679 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)

[fwddev]

I have restored my main.sh and rebuilt my DNS with no change.

My Site works but admin functions are VERY slow and SSHing into the server takes forever.

Any way to get this named DNS service to start?

All this happened after an auto update that happened over the weekend since then I have turned off auto updates as I do not need the extra unplanned headache.

[udimaster]

no meu caso tive que excluir todas as entradas de dns e consegui re-startar o servidor named