Author Topic: BIND DNS Server Failed - Help  (Read 974 times)

0 Members and 1 Guest are viewing this topic.

Offline
*
BIND DNS Server Failed - Help
« on: January 04, 2020, 11:09:10 PM »
-- Subject: Unit varnish.service has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit varnish.service has begun shutting down.
Jan 04 20:07:44 vps.sm150393.site varnishd[1206]: Manager got SIGINT
Jan 04 20:07:44 vps.sm150393.site varnishd[1206]: Stopping Child
Jan 04 20:07:45 vps.sm150393.site varnishd[1206]: Child (1694) died signal=15
Jan 04 20:07:45 vps.sm150393.site varnishd[1206]: Child cleanup complete
Jan 04 20:07:45 vps.sm150393.site systemd[1]: Stopped Varnish Cache, a high-performance HTTP accelerator.
-- Subject: Unit varnish.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit varnish.service has finished shutting down.
Jan 04 20:07:45 vps.sm150393.site systemd[1]: Starting Varnish Cache, a high-performance HTTP accelerator...
-- Subject: Unit varnish.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit varnish.service has begun starting up.
Jan 04 20:07:46 vps.sm150393.site varnishd[15154]: Debug: Platform: Linux,3.10.0-1062.9.1.el7.x86_64,x86_64,-junix,-smalloc,-smalloc,-hcritbit
Jan 04 20:07:46 vps.sm150393.site varnishd[15155]: Platform: Linux,3.10.0-1062.9.1.el7.x86_64,x86_64,-junix,-smalloc,-smalloc,-hcritbit
Jan 04 20:07:46 vps.sm150393.site varnishd[15154]: Debug: Child (15165) Started
Jan 04 20:07:46 vps.sm150393.site varnishd[15155]: Child (15165) Started
Jan 04 20:07:46 vps.sm150393.site varnishd[15155]: Child (15165) said Child starts
Jan 04 20:07:46 vps.sm150393.site systemd[1]: Started Varnish Cache, a high-performance HTTP accelerator.
-- Subject: Unit varnish.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit varnish.service has finished starting up.
--
-- The start-up result is done.
Jan 04 20:07:47 vps.sm150393.site systemd[1]: Stopping nginx - high performance web server...
-- Subject: Unit nginx.service has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit nginx.service has begun shutting down.
Jan 04 20:07:47 vps.sm150393.site systemd[1]: Stopped nginx - high performance web server.
-- Subject: Unit nginx.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit nginx.service has finished shutting down.
Jan 04 20:07:47 vps.sm150393.site systemd[1]: Starting nginx - high performance web server...
-- Subject: Unit nginx.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit nginx.service has begun starting up.
Jan 04 20:07:47 vps.sm150393.site nginx[15391]: nginx: [warn] the "ssl" directive is deprecated, use the "listen ... ssl" directive instead in /etc/nginx/conf.d/hostname-ssl.conf:8
Jan 04 20:07:47 vps.sm150393.site nginx[15391]: nginx: [warn] the "ssl" directive is deprecated, use the "listen ... ssl" directive instead in /etc/nginx/conf.d/vhosts/estrelinhamagica.com.br.ssl.conf:8
Jan 04 20:07:47 vps.sm150393.site nginx[15391]: nginx: [warn] the "ssl" directive is deprecated, use the "listen ... ssl" directive instead in /etc/nginx/conf.d/vhosts/sm150393.site.ssl.conf:8
Jan 04 20:07:47 vps.sm150393.site nginx[15391]: nginx: [warn] conflicting server name "vps.sm150393.site" on 173.212.206.155:80, ignored
Jan 04 20:07:47 vps.sm150393.site systemd[1]: Started nginx - high performance web server.
-- Subject: Unit nginx.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit nginx.service has finished starting up.
--
-- The start-up result is done.
Jan 04 20:07:50 vps.sm150393.site systemd[1]: Stopping MariaDB 10.1.43 database server...
-- Subject: Unit mariadb.service has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mariadb.service has begun shutting down.
Jan 04 20:07:50 vps.sm150393.site mysqld[1394]: 2020-01-04 20:07:50 140130173601536 [Note] /usr/sbin/mysqld: Normal shutdown
Jan 04 20:07:50 vps.sm150393.site mysqld[1394]: 2020-01-04 20:07:50 140130173601536 [Note] Event Scheduler: Purging the queue. 0 events
Jan 04 20:07:50 vps.sm150393.site mysqld[1394]: 2020-01-04 20:07:50 140129398134528 [Note] InnoDB: FTS optimize thread exiting.
Jan 04 20:07:50 vps.sm150393.site mysqld[1394]: 2020-01-04 20:07:50 140130173601536 [Note] InnoDB: Starting shutdown...
Jan 04 20:07:50 vps.sm150393.site postfix/smtpd[14652]: warning: hostname static.vnpt.vn does not resolve to address 14.187.37.93
Jan 04 20:07:50 vps.sm150393.site postfix/smtpd[14652]: connect from unknown[14.187.37.93]
Jan 04 20:07:51 vps.sm150393.site mysqld[1394]: 2020-01-04 20:07:51 140130173601536 [Note] InnoDB: Waiting for page_cleaner to finish flushing of buffer pool
Jan 04 20:07:51 vps.sm150393.site kernel: Firewall: *TCP_IN Blocked* IN=eth0 OUT= MAC=00:50:56:3d:60:8c:28:99:3a:4d:23:91:08:00 SRC=185.176.27.118 DST=173.212.206.155 LEN=40 TOS=0x00 PREC=0x00 TTL=249 ID=63583 PROTO=TCP SPT=50222 DPT=7690 WINDOW=1024 RES=0x00 SYN URGP=0
Jan 04 20:07:52 vps.sm150393.site mysqld[1394]: 2020-01-04 20:07:52 140130173601536 [Note] InnoDB: Shutdown completed; log sequence number 1862806360
Jan 04 20:07:52 vps.sm150393.site mysqld[1394]: 2020-01-04 20:07:52 140130173601536 [Note] /usr/sbin/mysqld: Shutdown complete
Jan 04 20:07:52 vps.sm150393.site systemd[1]: Stopped MariaDB 10.1.43 database server.
-- Subject: Unit mariadb.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mariadb.service has finished shutting down.
Jan 04 20:07:52 vps.sm150393.site systemd[1]: Starting MariaDB 10.1.43 database server...
-- Subject: Unit mariadb.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mariadb.service has begun starting up.
Jan 04 20:07:53 vps.sm150393.site mysqld[15499]: 2020-01-04 20:07:53 140051392088320 [Warning] option 'table_open_cache': unsigned value 8 adjusted to 10
Jan 04 20:07:53 vps.sm150393.site mysqld[15499]: 2020-01-04 20:07:53 140051392088320 [Note] /usr/sbin/mysqld (mysqld 10.1.43-MariaDB) starting as process 15499 ...
Jan 04 20:07:53 vps.sm150393.site mysqld[15499]: 2020-01-04 20:07:53 140051392088320 [Note] InnoDB: Using mutexes to ref count buffer pool pages
Jan 04 20:07:53 vps.sm150393.site mysqld[15499]: 2020-01-04 20:07:53 140051392088320 [Note] InnoDB: The InnoDB memory heap is disabled
Jan 04 20:07:53 vps.sm150393.site mysqld[15499]: 2020-01-04 20:07:53 140051392088320 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
Jan 04 20:07:53 vps.sm150393.site mysqld[15499]: 2020-01-04 20:07:53 140051392088320 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
Jan 04 20:07:53 vps.sm150393.site mysqld[15499]: 2020-01-04 20:07:53 140051392088320 [Note] InnoDB: Compressed tables use zlib 1.2.7
Jan 04 20:07:53 vps.sm150393.site mysqld[15499]: 2020-01-04 20:07:53 140051392088320 [Note] InnoDB: Using Linux native AIO
Jan 04 20:07:53 vps.sm150393.site mysqld[15499]: 2020-01-04 20:07:53 140051392088320 [Note] InnoDB: Using SSE crc32 instructions
Jan 04 20:07:53 vps.sm150393.site mysqld[15499]: 2020-01-04 20:07:53 140051392088320 [Note] InnoDB: Initializing buffer pool, size = 512.0M
Jan 04 20:07:53 vps.sm150393.site mysqld[15499]: 2020-01-04 20:07:53 140051392088320 [Note] InnoDB: Completed initialization of buffer pool
Jan 04 20:07:53 vps.sm150393.site mysqld[15499]: 2020-01-04 20:07:53 140051392088320 [Note] InnoDB: Highest supported file format is Barracuda.
Jan 04 20:07:53 vps.sm150393.site mysqld[15499]: 2020-01-04 20:07:53 140051392088320 [Note] InnoDB: 128 rollback segment(s) are active.
Jan 04 20:07:53 vps.sm150393.site mysqld[15499]: 2020-01-04 20:07:53 140051392088320 [Note] InnoDB: Waiting for purge to start
Jan 04 20:07:53 vps.sm150393.site mysqld[15499]: 2020-01-04 20:07:53 140051392088320 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.45-86.1 started; log sequence number 1862806360
Jan 04 20:07:53 vps.sm150393.site mysqld[15499]: 2020-01-04 20:07:53 140051392088320 [Note] Plugin 'FEEDBACK' is disabled.
Jan 04 20:07:53 vps.sm150393.site mysqld[15499]: 2020-01-04 20:07:53 140050306168576 [Note] InnoDB: Dumping buffer pool(s) not yet started
Jan 04 20:07:53 vps.sm150393.site mysqld[15499]: 2020-01-04 20:07:53 140051392088320 [Note] Server socket created on IP: '::'.
Jan 04 20:07:53 vps.sm150393.site mysqld[15499]: 2020-01-04 20:07:53 140051392088320 [Note] /usr/sbin/mysqld: ready for connections.
Jan 04 20:07:53 vps.sm150393.site mysqld[15499]: Version: '10.1.43-MariaDB'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MariaDB Server
Jan 04 20:07:53 vps.sm150393.site systemd[1]: Started MariaDB 10.1.43 database server.
-- Subject: Unit mariadb.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mariadb.service has finished starting up.
--
-- The start-up result is done.
Jan 04 20:07:54 vps.sm150393.site kernel: Firewall: *TCP_IN Blocked* IN=eth0 OUT= MAC=00:50:56:3d:60:8c:28:99:3a:4d:23:91:08:00 SRC=185.176.27.170 DST=173.212.206.155 LEN=40 TOS=0x00 PREC=0x00 TTL=249 ID=64576 PROTO=TCP SPT=45121 DPT=17843 WINDOW=1024 RES=0x00 SYN URGP=0
Jan 04 20:07:56 vps.sm150393.site postfix/smtpd[14652]: warning: unknown[14.187.37.93]: SASL PLAIN authentication failed:
Jan 04 20:07:56 vps.sm150393.site 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.
Jan 04 20:07:56 vps.sm150393.site 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.
Jan 04 20:07:56 vps.sm150393.site 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.
Jan 04 20:07:56 vps.sm150393.site bash[15561]: zone localhost.localdomain/IN: loaded serial 0
Jan 04 20:07:56 vps.sm150393.site bash[15561]: zone localhost/IN: loaded serial 0
Jan 04 20:07:56 vps.sm150393.site bash[15561]: zone 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa/IN: loaded serial 0
Jan 04 20:07:56 vps.sm150393.site bash[15561]: zone 1.0.0.127.in-addr.arpa/IN: loaded serial 0
Jan 04 20:07:56 vps.sm150393.site bash[15561]: zone 0.in-addr.arpa/IN: loaded serial 0
Jan 04 20:07:56 vps.sm150393.site bash[15561]: zone ns1.sm150393.site/IN: loaded serial 2013071600
Jan 04 20:07:56 vps.sm150393.site bash[15561]: zone ns2.sm150393.site/IN: loaded serial 2013071600
Jan 04 20:07:56 vps.sm150393.site bash[15561]: zone sm150393.site/IN: loaded serial 2019112190
Jan 04 20:07:56 vps.sm150393.site bash[15561]: /var/named/vps.sm150393.site.db:28: ignoring out-of-zone data (ns1.sm150393.site)
Jan 04 20:07:56 vps.sm150393.site bash[15561]: /var/named/vps.sm150393.site.db:29: ignoring out-of-zone data (ns2.sm150393.site)
Jan 04 20:07:56 vps.sm150393.site bash[15561]: /var/named/vps.sm150393.site.db:33: file does not end with newline
Jan 04 20:07:56 vps.sm150393.site bash[15561]: zone vps.sm150393.site/IN: loaded serial 2019112208
Jan 04 20:07:56 vps.sm150393.site bash[15561]: /var/named/agrmarcasepatentes.com.br.db:28: ignoring out-of-zone data (ns1.sm150393.site)
Jan 04 20:07:56 vps.sm150393.site bash[15561]: /var/named/agrmarcasepatentes.com.br.db:29: ignoring out-of-zone data (ns2.sm150393.site)
Jan 04 20:07:56 vps.sm150393.site bash[15561]: /var/named/agrmarcasepatentes.com.br.db:30: ignoring out-of-zone data (vps.sm150393.site)
Jan 04 20:07:56 vps.sm150393.site bash[15561]: /var/named/agrmarcasepatentes.com.br.db:30: file does not end with newline
Jan 04 20:07:56 vps.sm150393.site bash[15561]: zone agrmarcasepatentes.com.br/IN: loaded serial 2019112208
Jan 04 20:07:56 vps.sm150393.site bash[15561]: dns_master_load: /var/named/fotolembranca.com.br.db:24: www.fotolembranca.com.br: multiple RRs of singleton type
Jan 04 20:07:56 vps.sm150393.site bash[15561]: /var/named/fotolembranca.com.br.db:28: ignoring out-of-zone data (ns1.sm150393.site)
Jan 04 20:07:56 vps.sm150393.site bash[15561]: /var/named/fotolembranca.com.br.db:29: ignoring out-of-zone data (ns2.sm150393.site)
Jan 04 20:07:56 vps.sm150393.site bash[15561]: /var/named/fotolembranca.com.br.db:30: ignoring out-of-zone data (vps.sm150393.site)
Jan 04 20:07:56 vps.sm150393.site bash[15561]: zone fotolembranca.com.br/IN: loading from master file /var/named/fotolembranca.com.br.db failed: multiple RRs of singleton type
Jan 04 20:07:56 vps.sm150393.site bash[15561]: zone fotolembranca.com.br/IN: not loaded due to errors.
Jan 04 20:07:56 vps.sm150393.site bash[15561]: _default/fotolembranca.com.br/IN: multiple RRs of singleton type
Jan 04 20:07:56 vps.sm150393.site bash[15561]: dns_master_load: /var/named/cdn.fotolembranca.com.br.db:24: www.cdn.fotolembranca.com.br: multiple RRs of singleton type
Jan 04 20:07:56 vps.sm150393.site bash[15561]: /var/named/cdn.fotolembranca.com.br.db:28: ignoring out-of-zone data (ns1.sm150393.site)
Jan 04 20:07:56 vps.sm150393.site bash[15561]: /var/named/cdn.fotolembranca.com.br.db:29: ignoring out-of-zone data (ns2.sm150393.site)
Jan 04 20:07:56 vps.sm150393.site bash[15561]: /var/named/cdn.fotolembranca.com.br.db:30: ignoring out-of-zone data (vps.sm150393.site)
Jan 04 20:07:56 vps.sm150393.site bash[15561]: zone cdn.fotolembranca.com.br/IN: loading from master file /var/named/cdn.fotolembranca.com.br.db failed: multiple RRs of singleton type
Jan 04 20:07:56 vps.sm150393.site bash[15561]: zone cdn.fotolembranca.com.br/IN: not loaded due to errors.
Jan 04 20:07:56 vps.sm150393.site bash[15561]: _default/cdn.fotolembranca.com.br/IN: multiple RRs of singleton type
Jan 04 20:07:56 vps.sm150393.site bash[15561]: zone dicasdafer.com.br/IN: loaded serial 2019112566
Jan 04 20:07:56 vps.sm150393.site bash[15561]: zone emporiodosucesso.com.br/IN: loaded serial 2019112566
Jan 04 20:07:56 vps.sm150393.site bash[15561]: zone insistimento.com.br/IN: loaded serial 2019112566
Jan 04 20:07:56 vps.sm150393.site bash[15561]: zone marcomaia.com.br/IN: loaded serial 2019112566
Jan 04 20:07:56 vps.sm150393.site bash[15561]: zone projetoperolas.com.br/IN: loaded serial 2019112567
Jan 04 20:07:56 vps.sm150393.site bash[15561]: zone rodrigosouto.com.br/IN: loaded serial 2019112567
Jan 04 20:07:56 vps.sm150393.site bash[15561]: zone vireiviral.com.br/IN: loaded serial 2019112567
Jan 04 20:07:56 vps.sm150393.site bash[15561]: zone pontorep.com.br/IN: loaded serial 2019112567
Jan 04 20:07:56 vps.sm150393.site bash[15561]: /var/named/estrelinhamagica.com.br.db:29: ignoring out-of-zone data (ns1.sm150393.site)
Jan 04 20:07:56 vps.sm150393.site bash[15561]: /var/named/estrelinhamagica.com.br.db:30: ignoring out-of-zone data (ns2.sm150393.site)
Jan 04 20:07:56 vps.sm150393.site bash[15561]: /var/named/estrelinhamagica.com.br.db:31: ignoring out-of-zone data (vps.sm150393.site)
Jan 04 20:07:56 vps.sm150393.site bash[15561]: /var/named/estrelinhamagica.com.br.db:32: file does not end with newline
Jan 04 20:07:56 vps.sm150393.site bash[15561]: zone estrelinhamagica.com.br/IN: loaded serial 2019112567
Jan 04 20:07:56 vps.sm150393.site bash[15561]: zone alegresvegetarianos.com/IN: loaded serial 2019112568
Jan 04 20:07:56 vps.sm150393.site systemd[1]: named.service: control process exited, code=exited status=1
Jan 04 20:07:56 vps.sm150393.site 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.
Jan 04 20:07:56 vps.sm150393.site systemd[1]: Unit named.service entered failed state.
Jan 04 20:07:56 vps.sm150393.site systemd[1]: named.service failed.
Jan 04 20:07:56 vps.sm150393.site postfix/smtpd[14652]: lost connection after AUTH from unknown[14.187.37.93]
Jan 04 20:07:56 vps.sm150393.site postfix/smtpd[14652]: disconnect from unknown[14.187.37.93]

Offline
*
Re: BIND DNS Server Failed - Help
« Reply #1 on: January 05, 2020, 09:20:04 AM »
Hi

you have to configure DNS properly . Set A records for your FQDN & NameServer .

Deatils:
How to Configure DNS properly for CentOS WebPanel on CentOS 7.6?


Offline
*****
Re: BIND DNS Server Failed - Help
« Reply #2 on: January 05, 2020, 10:42:47 AM »
I see too many errors there. And if you do not understand what they mean, I would recommend get a support with a system administrator and/or CWP support.
You can ask me to solve any problem with your server for some money in pm  ;)
Services Monitoring & RBL Monitoring
http://centos-webpanel.com/services-monitor
Join our Development Team and get paid !
http://centos-webpanel.com/develope-modules-for-cwp

Installation Instructions
http://centos-webpanel.com/installation-instructions
Get Fast Support Here
http://centos-webpanel.com/support-services