After Update Problems with DNS
After Update Problems with DNS
Hey everyone
First thanks for the script it's amazing and it's free!!
So I am using for 5 months vesta no problems at all before the update!!
After the update when I add a new A entry for a domain the Named server crashes and just restart when I delete the entry.
I am able to edit manual the DNS but why this is happening?
Should I reinstall from zero again?
I did not post before because I was hoping for a new update that would fix this. probably it's not just me.
Works fine when I add a new domain!! The problem it's when you edit the zone
Thank you
First thanks for the script it's amazing and it's free!!
So I am using for 5 months vesta no problems at all before the update!!
After the update when I add a new A entry for a domain the Named server crashes and just restart when I delete the entry.
I am able to edit manual the DNS but why this is happening?
Should I reinstall from zero again?
I did not post before because I was hoping for a new update that would fix this. probably it's not just me.
Works fine when I add a new domain!! The problem it's when you edit the zone
Thank you
Re: After Update Problems with DNS
Hi
You need say us more details,
What SO you use ?
What about logs ?
What say named when you restart etc
You need say us more details,
What SO you use ?
What about logs ?
What say named when you restart etc
Re: After Update Problems with DNS
Sorry
My OS it's CentOS
The error
Thank you
My OS it's CentOS
The error
Code: Select all
[root@hostmaster dns]# service named restart
Redirecting to /bin/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@hostmaster dns]# 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 2016-07-18 02:14:05 PDT; 19s ago
Process: 30601 ExecStop=/bin/sh -c /usr/sbin/rndc stop > /dev/null 2>&1 || /bin/kill -TERM $MAINPID (code=exited, status=0/SUCCESS)
Process: 30527 ExecReload=/bin/sh -c /usr/sbin/rndc reload > /dev/null 2>&1 || /bin/kill -HUP $MAINPID (code=exited, status=0/SUCCESS)
Process: 28025 ExecStart=/usr/sbin/named -u named $OPTIONS (code=exited, status=0/SUCCESS)
Process: 30610 ExecStartPre=/bin/bash -c if [ ! "$DISABLE_ZONE_CHECKING" == "yes" ]; then /usr/sbin/named-checkconf -z /etc/named.conf; el se echo "Checking of zone files is disabled"; fi (code=exited, status=1/FAILURE)
Main PID: 28028 (code=exited, status=0/SUCCESS)
Jul 18 02:14:05 hostmaster.siweb.co bash[30610]: dns_rdata_fromtext: /home/admin/conf/dns/ajudacerta.com.br.db:2: near 'root..': empty label
Jul 18 02:14:05 hostmaster.siweb.co bash[30610]: zone ajudacerta.com.br/IN: loading from master file /home/admin/conf/dns/ajudacer...y label
Jul 18 02:14:05 hostmaster.siweb.co bash[30610]: zone ajudacerta.com.br/IN: not loaded due to errors.
Jul 18 02:14:05 hostmaster.siweb.co bash[30610]: _default/ajudacerta.com.br/IN: empty label
Jul 18 02:14:05 hostmaster.siweb.co systemd[1]: named.service: control process exited, code=exited status=1
Jul 18 02:14:05 hostmaster.siweb.co systemd[1]: Failed to start Berkeley Internet Name Domain (DNS).
Jul 18 02:14:05 hostmaster.siweb.co systemd[1]: Unit named.service entered failed state.
Jul 18 02:14:05 hostmaster.siweb.co systemd[1]: named.service failed.
Re: After Update Problems with DNS
Code: Select all
Jul 18 09:34:53 hostmaster.siweb.co avahi-daemon[459]: Registering new address record for fe80::601:aeff:fe16:f102 on eth1.*.
Jul 18 09:34:58 hostmaster.siweb.co dhclient[22678]: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 6 (xid=0x27dc81b)
Jul 18 09:34:59 hostmaster.siweb.co polkitd[500]: Registered Authentication Agent for unix-process:22683:161578189 (system bus name :1.22721 [/usr/bin/pkttyagent --notify-fd 5 --fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
Jul 18 09:34:59 hostmaster.siweb.co systemd[1]: Stopping Berkeley Internet Name Domain (DNS)...
-- Subject: Unit named.service has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit named.service has begun shutting down.
Jul 18 09:34:59 hostmaster.siweb.co named[32727]: received control channel command 'stop'
Jul 18 09:34:59 hostmaster.siweb.co named[32727]: shutting down: flushing changes
Jul 18 09:34:59 hostmaster.siweb.co named[32727]: stopping command channel on 127.0.0.1#953
Jul 18 09:34:59 hostmaster.siweb.co named[32727]: stopping command channel on ::1#953
Jul 18 09:34:59 hostmaster.siweb.co named[32727]: no longer listening on 127.0.0.1#53
Jul 18 09:34:59 hostmaster.siweb.co named[32727]: no longer listening on 45.55.8.211#53
Jul 18 09:34:59 hostmaster.siweb.co named[32727]: no longer listening on 10.12.0.5#53
Jul 18 09:34:59 hostmaster.siweb.co named[32727]: no longer listening on 45.55.114.18#53
Jul 18 09:34:59 hostmaster.siweb.co named[32727]: exiting
Jul 18 09:34:59 hostmaster.siweb.co systemd[1]: Starting Generate rndc key for BIND (DNS)...
-- Subject: Unit named-setup-rndc.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit named-setup-rndc.service has begun starting up.
Jul 18 09:34:59 hostmaster.siweb.co systemd[1]: Started Generate rndc key for BIND (DNS).
-- Subject: Unit named-setup-rndc.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit named-setup-rndc.service has finished starting up.
--
-- The start-up result is done.
Jul 18 09:34:59 hostmaster.siweb.co systemd[1]: Starting Berkeley Internet Name Domain (DNS)...
-- Subject: Unit named.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit named.service has begun starting up.
Jul 18 09:34:59 hostmaster.siweb.co bash[22707]: zone siweb.co/IN: loaded serial 2016071202
Jul 18 09:34:59 hostmaster.siweb.co bash[22707]: zone irenekimart.com/IN: loaded serial 2016022403
Jul 18 09:34:59 hostmaster.siweb.co bash[22707]: zone ticagencia.com.br/IN: loaded serial 2016022804
Jul 18 09:34:59 hostmaster.siweb.co bash[22707]: zone donadoroteiapizzas.com.br/IN: loaded serial 2016030203
Jul 18 09:34:59 hostmaster.siweb.co bash[22707]: zone hostmaster.siweb.co/IN: loaded serial 2016030203
Jul 18 09:34:59 hostmaster.siweb.co bash[22707]: zone kiadesivo.com.br/IN: loaded serial 2016050503
Jul 18 09:34:59 hostmaster.siweb.co bash[22707]: dns_rdata_fromtext: /home/admin/conf/dns/ajudacerta.com.br.db:2: near 'root..': empty label
Jul 18 09:34:59 hostmaster.siweb.co bash[22707]: zone ajudacerta.com.br/IN: loading from master file /home/admin/conf/dns/ajudacerta.com.br.db failed: empty label
Jul 18 09:34:59 hostmaster.siweb.co bash[22707]: zone ajudacerta.com.br/IN: not loaded due to errors.
Jul 18 09:34:59 hostmaster.siweb.co bash[22707]: _default/ajudacerta.com.br/IN: empty label
Jul 18 09:34:59 hostmaster.siweb.co systemd[1]: named.service: control process exited, code=exited status=1
Jul 18 09:34:59 hostmaster.siweb.co systemd[1]: Failed to start Berkeley Internet Name Domain (DNS).
-- Subject: Unit named.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit named.service has failed.
--
-- The result is failed.
Jul 18 09:34:59 hostmaster.siweb.co systemd[1]: Unit named.service entered failed state.
Jul 18 09:34:59 hostmaster.siweb.co systemd[1]: named.service failed.
Jul 18 09:34:59 hostmaster.siweb.co bash[22707]: zone weminemue.com/IN: loaded serial 2016071602
Jul 18 09:34:59 hostmaster.siweb.co polkitd[500]: Unregistered Authentication Agent for unix-process:22683:161578189 (system bus name :1.22721, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
Jul 18 09:35:01 hostmaster.siweb.co systemd[1]: Started Session 11346 of user admin.
-- Subject: Unit session-11346.scope has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-11346.scope has finished starting up.
--
-- The start-up result is done.
Jul 18 09:35:01 hostmaster.siweb.co systemd[1]: Starting Session 11346 of user admin.
-- Subject: Unit session-11346.scope has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-11346.scope has begun starting up.
Jul 18 09:35:01 hostmaster.siweb.co systemd[1]: Started Session 11345 of user admin.
-- Subject: Unit session-11345.scope has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-11345.scope has finished starting up.
--
-- The start-up result is done.
Jul 18 09:35:01 hostmaster.siweb.co systemd[1]: Starting Session 11345 of user admin.
-- Subject: Unit session-11345.scope has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-11345.scope has begun starting up.
Jul 18 09:35:01 hostmaster.siweb.co CROND[22715]: (admin) CMD (sudo /usr/local/vesta/bin/v-update-sys-rrd)
Jul 18 09:35:01 hostmaster.siweb.co CROND[22716]: (admin) CMD (sudo /usr/local/vesta/bin/v-update-sys-queue backup)
Jul 18 09:35:04 hostmaster.siweb.co dhclient[22678]: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7 (xid=0x27dc81b)
Thanks !!!
Re: After Update Problems with DNS
I will try to rebuild probably will fix!!
I think must be something about permission. that happens in all domains in the server after the update before was just fine!!
I will try now and I will post the result
I think must be something about permission. that happens in all domains in the server after the update before was just fine!!
I will try now and I will post the result
Re: After Update Problems with DNS
Did not worked!!
But the problem the file becomes corrupted after the Vesta edit for some reason!!
I try create a new domain and worked but when I add an A entry the named crashes. I can ADD the entry manual editing the file and the named does not crash after I edit manual. Just using the Vesta. has to be some bug from the new version that does not edit properly the file .db
I am using CentOS 7.2
But the problem the file becomes corrupted after the Vesta edit for some reason!!
I try create a new domain and worked but when I add an A entry the named crashes. I can ADD the entry manual editing the file and the named does not crash after I edit manual. Just using the Vesta. has to be some bug from the new version that does not edit properly the file .db
I am using CentOS 7.2
Re: After Update Problems with DNS
I am really thinking about to install from zero into another machine. and then migrate the accounts I just have like 5 so should no be a pain.
I will install a new VestaCP but now I will go with Ubuntu this time
and I will keep the autoupdate off
I will install a new VestaCP but now I will go with Ubuntu this time
and I will keep the autoupdate off
Re: After Update Problems with DNS
Thank you so much!!!
Re: After Update Problems with DNS
Is a bug yes, you can trace it here: https://bugs.vestacp.com/issues/283
You can also use temporary fix -> https://github.com/serghey-rodin/vesta/pull/756/files
Resolved, will be in v17 release.
You can also use temporary fix -> https://github.com/serghey-rodin/vesta/pull/756/files
Resolved, will be in v17 release.
Re: After Update Problems with DNS
What need do after adding changes in file main.sh? I do "service vesta restart" but nothing, problem persist.