Vesta Control Panel - Forum

Community Forum

Skip to content

Advanced search
  • Quick links
    • Main site
    • Github repo
    • Google Search
  • FAQ
  • Login
  • Register
  • Board index Main Section DNS Server
  • Search

Error: named restart failed

Questions regarding the DNS Server
BIND
Post Reply
  • Print view
Advanced search
18 posts
  • Previous
  • 1
  • 2
shonir
Posts: 42
Joined: Tue Sep 20, 2016 10:58 am
Contact:
Contact shonir
Website Skype

Os: CentOS 6x
Web: apache + nginx
Re: Error: named restart failed
  • Quote

Post by shonir » Tue Mar 07, 2017 7:29 pm

when i try to delete user its delete domain under user account but not deleting user and given error Error: named restart failed<br>Error: dns domain deletion failed
Top

shonir
Posts: 42
Joined: Tue Sep 20, 2016 10:58 am
Contact:
Contact shonir
Website Skype

Os: CentOS 6x
Web: apache + nginx
Re: Error: named restart failed
  • Quote

Post by shonir » Tue Mar 07, 2017 8:34 pm

i just notic All website that is on cloudflare working fine and also emails working good. other wib site that using my private nameserver not working.
Top

shonir
Posts: 42
Joined: Tue Sep 20, 2016 10:58 am
Contact:
Contact shonir
Website Skype

Os: CentOS 6x
Web: apache + nginx
Re: Error: named restart failed
  • Quote

Post by shonir » Wed Mar 08, 2017 7:06 am

i fixed permission problem using below commands and now named started

Code: Select all

chown named:named /etc/rndc.key
chmod 644 /etc/rndc.key

chmod 644 /etc/named.conf

service named start


now the problem is vesta admin showing date created date 01 Jan 1970 and not taking backup daily like other up to 40 accounts working fine.
Top

skurudo
VestaCP Team
Posts: 8099
Joined: Fri Dec 26, 2014 2:23 pm
Contact:
Contact skurudo
Website Facebook Google+ Skype
Twitter

Re: Error: named restart failed
  • Quote

Post by skurudo » Thu Mar 09, 2017 12:16 pm

shonir wrote:now the problem is vesta admin showing date created date 01 Jan 1970 and not taking backup daily like other up to 40 accounts working fine.
Show this where? In cron?
What time is it on server?

Code: Select all

date
Top

shonir
Posts: 42
Joined: Tue Sep 20, 2016 10:58 am
Contact:
Contact shonir
Website Skype

Os: CentOS 6x
Web: apache + nginx
Re: Error: named restart failed
  • Quote

Post by shonir » Thu Mar 09, 2017 1:09 pm

skurudo wrote:
shonir wrote:now the problem is vesta admin showing date created date 01 Jan 1970 and not taking backup daily like other up to 40 accounts working fine.
Show this where? In cron?
What time is it on server?

Code: Select all

date

Result Is

Thu Mar 9 18:04:14 PKT 2017

Image
Top

twister5800
Posts: 6
Joined: Tue May 24, 2016 3:31 pm

Re: Error: named restart failed
  • Quote

Post by twister5800 » Wed May 10, 2017 5:49 am

I too have this issue on Centos 7:

sudo 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 Wed 2017-05-10 07:41:28 CEST; 59s ago
Process: 16212 ExecStop=/bin/sh -c /usr/sbin/rndc stop > /dev/null 2>&1 || /bin/kill -TERM $MAINPID (code=exited, status=0/SUCCESS)
Process: 15847 ExecReload=/bin/sh -c /usr/sbin/rndc reload > /dev/null 2>&1 || /bin/kill -HUP $MAINPID (code=exited, status=0/SUCCESS)
Process: 18737 ExecStart=/usr/sbin/named -u named $OPTIONS (code=exited, status=1/FAILURE)
Process: 18734 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=0/SUCCESS)
Main PID: 14938 (code=exited, status=0/SUCCESS)

May 10 07:41:28 web01.domain.dk named[18739]: found 2 CPUs, using 2 worker threads
May 10 07:41:28 web01.domain.dk named[18739]: using 2 UDP listeners per interface
May 10 07:41:28 web01.domain.dk named[18739]: using up to 4096 sockets
May 10 07:41:28 web01.domain.dk named[18739]: loading configuration from '/etc/named.conf'
May 10 07:41:28 web01.domain.dk named[18739]: open: /etc/named.conf: permission denied
May 10 07:41:28 web01.domain.dk named[18739]: loading configuration: permission denied
May 10 07:41:28 web01.domain.dk systemd[1]: named.service: control process exited, code=exited status=1
May 10 07:41:28 web01.domain.dk systemd[1]: Failed to start Berkeley Internet Name Domain (DNS).
May 10 07:41:28 web01.domain.dk systemd[1]: Unit named.service entered failed state.
May 10 07:41:28 web01.domain.dk systemd[1]: named.service failed.

When doing chown on named.conf, things may work, but only until I add new zones or change anything via vestacp in dns config :-(

From install script, used theese two commands:

#----------------------------------------------------------#
# Configure Bind #
#----------------------------------------------------------#

chown root:named /etc/named.conf
chmod 640 /etc/named.conf

But nevertheless it's not working ?!

UPDATE:
Had changed allow-transfer to any for testing purposes, did open named.conf in nano and changed back to "none", now named started, did nano change the permissions on the file?

Best regards
Martin
Top

twister5800
Posts: 6
Joined: Tue May 24, 2016 3:31 pm

Re: Error: named restart failed
  • Quote

Post by twister5800 » Wed May 10, 2017 7:05 am

Fixed it!

There where more user errors here.

i had the vestacp registered as web01.domain.dk but I created domain.dk as a standalone domain because it's needed for corporate profile, that made named say access denied, when that zone was removed, named started :-O
Top

nikk
Posts: 19
Joined: Fri Nov 22, 2019 10:43 am

Os: CentOS 6x
Web: apache
Re: Error: named restart failed
  • Quote

Post by nikk » Thu Dec 05, 2019 2:30 pm

twister5800, Help me to solve the same problem, what to do, what file prvit?
Top


Post Reply
  • Print view

18 posts
  • Previous
  • 1
  • 2

Return to “DNS Server”



  • Board index
  • All times are UTC
  • Delete all board cookies
  • The team
Powered by phpBB® Forum Software © phpBB Limited
*Original Author: Brad Veryard
*Updated to 3.2 by MannixMD
 

 

Login  •  Register

I forgot my password