Vesta Control Panel - Forum

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

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.

i fixed permission problem using below commands and now named started

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.

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?

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

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

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

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