LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 08-03-2019, 12:45 PM   #1
nk96verma@gmail.com
LQ Newbie
 
Registered: Aug 2019
Posts: 4

Rep: Reputation: Disabled
Exclamation Named Service failed to start


I have website on godaddy vps server(linux).I am facing some issues related to dns from last 1 week only.
I was something like "ERR DNS Probe NX Domain". By doing some research i found out that the error is due to named failed to start(/var/log/messages) i have tried to fix that by the below command
"systemctl enable named.service && systemctl start named.service"

but it works fine for 3-6hrs very well but website goes offline after that.Currently i need to restart the dns server everytime and it works.

But i am looking for permanent solution for the issue.
Any help to solve the issue will be appreciated.
 
Old 08-03-2019, 01:44 PM   #2
scasey
LQ Veteran
 
Registered: Feb 2013
Location: Tucson, AZ, USA
Distribution: CentOS 7.8.2003
Posts: 5,475

Rep: Reputation: 2100Reputation: 2100Reputation: 2100Reputation: 2100Reputation: 2100Reputation: 2100Reputation: 2100Reputation: 2100Reputation: 2100Reputation: 2100Reputation: 2100
Quote:
Originally Posted by nk96verma@gmail.com View Post
I have website on godaddy vps server(linux).I am facing some issues related to dns from last 1 week only.
I was something like "ERR DNS Probe NX Domain". By doing some research i found out that the error is due to named failed to start(/var/log/messages) i have tried to fix that by the below command
"systemctl enable named.service && systemctl start named.service"

but it works fine for 3-6hrs very well but website goes offline after that.Currently i need to restart the dns server everytime and it works.

But i am looking for permanent solution for the issue.
Any help to solve the issue will be appreciated.
We're going to need a lot more information.
Please post, in code tags, the actual error messages you found in /var/log/messages. In particular, what is giving you the error you quoted?

Also post the result of systemctl status named.service both while things are working and while in a failure.
 
1 members found this post helpful.
Old 08-04-2019, 01:09 PM   #3
nk96verma@gmail.com
LQ Newbie
 
Registered: Aug 2019
Posts: 4

Original Poster
Rep: Reputation: Disabled
/var/log/messages data

Quote:
Originally Posted by nk96verma@gmail.com View Post
I have website on godaddy vps server(linux).I am facing some issues related to dns from last 1 week only.
I was something like "ERR DNS Probe NX Domain". By doing some research i found out that the error is due to named failed to start(/var/log/messages) i have tried to fix that by the below command
"systemctl enable named.service && systemctl start named.service"

but it works fine for 3-6hrs very well but website goes offline after that.Currently i need to restart the dns server everytime and it works.

But i am looking for permanent solution for the issue.
Any help to solve the issue will be appreciated.
Aug 4 08:25:41 s148-72-210-152 named[22448]: ----------------------------------------------------
Aug 4 08:25:41 s148-72-210-152 named[22448]: BIND 9 is maintained by Internet Systems Consortium,
Aug 4 08:25:41 s148-72-210-152 named[22448]: Inc. (ISC), a non-profit 501(c)(3) public-benefit
Aug 4 08:25:41 s148-72-210-152 named[22448]: corporation. Support and training for BIND 9 are
Aug 4 08:25:41 s148-72-210-152 named[22448]: available at https://www.isc.org/support
Aug 4 08:25:41 s148-72-210-152 named[22448]: ----------------------------------------------------
Aug 4 08:25:41 s148-72-210-152 named[22448]: adjusted limit on open files from 4096 to 1048576
Aug 4 08:25:41 s148-72-210-152 named[22448]: found 1 CPU, using 1 worker thread
Aug 4 08:25:41 s148-72-210-152 named[22448]: using 1 UDP listener per interface
Aug 4 08:25:41 s148-72-210-152 named[22448]: using up to 21000 sockets
Aug 4 08:25:41 s148-72-210-152 named[22448]: loading configuration from '/etc/named.conf'
Aug 4 08:25:41 s148-72-210-152 named[22448]: initializing GeoIP Country (IPv4) (type 1) DB
Aug 4 08:25:41 s148-72-210-152 named[22448]: GEO-106FREE 20180327 Build 1 Copyright (c) 2018 MaxMind Inc All Rights Reserved
Aug 4 08:25:41 s148-72-210-152 named[22448]: initializing GeoIP Country (IPv6) (type 12) DB
Aug 4 08:25:41 s148-72-210-152 named[22448]: GEO-106FREE 20180605 Build 1 Copyright (c) 2018 MaxMind Inc All Rights Reserved
Aug 4 08:25:41 s148-72-210-152 named[22448]: GeoIP City (IPv4) (type 2) DB not available
Aug 4 08:25:41 s148-72-210-152 named[22448]: GeoIP City (IPv4) (type 6) DB not available
Aug 4 08:25:41 s148-72-210-152 named[22448]: GeoIP City (IPv6) (type 30) DB not available
Aug 4 08:25:41 s148-72-210-152 named[22448]: GeoIP City (IPv6) (type 31) DB not available
Aug 4 08:25:41 s148-72-210-152 named[22448]: GeoIP Region (type 3) DB not available
Aug 4 08:25:41 s148-72-210-152 named[22448]: GeoIP Region (type 7) DB not available
Aug 4 08:25:41 s148-72-210-152 named[22448]: GeoIP ISP (type 4) DB not available
Aug 4 08:25:41 s148-72-210-152 named[22448]: GeoIP Org (type 5) DB not available
Aug 4 08:25:41 s148-72-210-152 named[22448]: GeoIP AS (type 9) DB not available
Aug 4 08:25:41 s148-72-210-152 named[22448]: GeoIP Domain (type 11) DB not available
Aug 4 08:25:41 s148-72-210-152 named[22448]: GeoIP NetSpeed (type 10) DB not available
Aug 4 08:25:41 s148-72-210-152 named[22448]: using default UDP/IPv4 port range: [1024, 65535]
Aug 4 08:25:41 s148-72-210-152 named[22448]: using default UDP/IPv6 port range: [1024, 65535]
Aug 4 08:25:41 s148-72-210-152 named[22448]: listening on IPv4 interface lo, 127.0.0.1#53
Aug 4 08:25:41 s148-72-210-152 named[22448]: listening on IPv4 interface eth0, 10.217.134.105#53
Aug 4 08:25:41 s148-72-210-152 named[22448]: listening on IPv4 interface eth0:1, 148.72.210.152#53
Aug 4 08:25:41 s148-72-210-152 named[22448]: generating session key for dynamic DNS
Aug 4 08:25:41 s148-72-210-152 named[22448]: sizing zone task pool based on 11 zones
Aug 4 08:25:41 s148-72-210-152 named[22448]: set up managed keys zone for view localhost_resolver, file '03641f096ea0ceb02e407a63ea6d9e42d7ceafabd8156336551aeae23ee060ed.mkeys'
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 10.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 16.172.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 17.172.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 18.172.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 19.172.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 20.172.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 21.172.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 22.172.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 23.172.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 24.172.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 25.172.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 26.172.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 27.172.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 28.172.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 29.172.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 30.172.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 31.172.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 168.192.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 64.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 65.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 66.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 67.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 68.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 69.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 70.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 71.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 72.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 73.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 74.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 75.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 76.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 77.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 78.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 79.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 80.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 81.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 82.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 83.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 84.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 85.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 86.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 87.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 88.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 89.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 90.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 91.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 92.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 93.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 94.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 95.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 96.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 97.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 98.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 99.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 100.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 101.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 102.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 103.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 104.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 105.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 106.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 107.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 108.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 109.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 110.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 111.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 112.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 113.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 114.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 115.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 116.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 117.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 118.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 119.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 120.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 121.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 122.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 123.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 124.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 125.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 126.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 127.100.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 127.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 254.169.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 2.0.192.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 100.51.198.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 113.0.203.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 255.255.255.255.IN-ADDR.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 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.0.IP6.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 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
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: D.F.IP6.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 8.E.F.IP6.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 9.E.F.IP6.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: A.E.F.IP6.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: B.E.F.IP6.ARPA
Aug 4 08:25:41 s148-72-210-152 named[22448]: automatic empty zone: view localhost_resolver: 8.B.D.0.1.0.0.2.IP6.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: set up managed keys zone for view internal, file '3bed2cb3a3acf7b6a8ef408420cc682d5520e26976d354254f528c965612054f.mkeys'
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 10.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 16.172.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 17.172.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 18.172.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 19.172.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 20.172.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 21.172.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 22.172.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 23.172.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 24.172.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 25.172.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 26.172.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 27.172.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 28.172.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 29.172.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 30.172.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 31.172.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 168.192.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 64.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 65.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 66.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 67.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 68.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 69.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 70.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 71.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 72.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 73.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 74.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 75.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 76.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 77.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 78.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 79.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 80.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 81.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 82.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 83.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 84.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 85.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 86.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 87.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 88.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 89.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 90.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 91.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 92.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 93.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 94.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 95.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 96.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 97.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 98.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 99.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 100.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 101.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 102.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 103.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 104.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 105.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 106.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 107.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 108.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 109.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 110.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 111.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 112.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 113.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 114.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 115.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 116.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 117.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 118.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 119.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 120.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 121.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 122.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 123.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 124.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 125.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 126.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 127.100.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 0.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 127.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 254.169.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 2.0.192.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 100.51.198.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 113.0.203.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 255.255.255.255.IN-ADDR.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 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.0.IP6.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 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
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: D.F.IP6.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 8.E.F.IP6.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 9.E.F.IP6.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: A.E.F.IP6.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: B.E.F.IP6.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: automatic empty zone: view internal: 8.B.D.0.1.0.0.2.IP6.ARPA
Aug 4 08:25:42 s148-72-210-152 named[22448]: set up managed keys zone for view external, file '3c4623849a49a53911c4a3e48d8cead8a1858960bccdea7a1b978d73ec2f06d7.mkeys'
Aug 4 08:25:42 s148-72-210-152 named[22448]: command channel listening on 127.0.0.1#953
Aug 4 08:25:42 s148-72-210-152 systemd: Started Berkeley Internet Name Domain (DNS).
Aug 4 09:49:26 s148-72-210-152 nydus-ex-api: INFO statusing nydus-ex
Aug 4 09:49:26 s148-72-210-152 systemd: Created slice User Slice of root.
Aug 4 09:49:26 s148-72-210-152 systemd: Started Session c11 of user root.
Aug 4 09:49:26 s148-72-210-152 nydus-ex-api: INFO {'stderr': '', 'args': ['/opt/nydus/bin/service.sh', 'nydus-ex', 'status'], 'returncode': 0, 'stdout': '● nydus-ex.service - nydus-ex\n Loaded: loaded (/usr/lib/systemd/system/nydus-ex.service; enabled; vendor preset: disabled)\n Active: active (running) since Wed 2019-07-31 10:19:22 MST; 3 days ago\n Main PID: 1940 (nydus-ex)\n CGroup: /system.slice/nydus-ex.service\n └─1940 /opt/nydus/pyvenv/bin/python3.5 /opt/nydus/pyvenv/bin/nydus-ex\n\nAug 04 01:32:15 s148-72-210-152.secureserver.net nydus-ex[1940]: ERROR (\'Failed to unlink %s\', \'/opt/nydus/executor/queue/processing-5b2f934eb69211e98d8efa163e541e42-ext\')\nAug 04 01:32:15 s148-72-210-152.secureserver.net nydus-ex[1940]: Traceback (most recent call last):\nAug 04 01:32:15 s148-72-210-152.secureserver.net nydus-ex[1940]: File "/opt/nydus/pyvenv/lib/python3.5/site-packages/archon/datasource/aqueue.py", line 429, in delete_item\nAug 04 01:32:15 s148-72-210-152.secureserver.net nydus-ex[1940]: os.unlink(processing_file)\nAug 04 01:32:15 s148-72-210-152.secureserver.net nydus-ex[1940]: FileNotFoundError: [Errno 2] No such file or directory: \'/opt/nydus/executor/queue/processing-5b2f934eb69211e98d8efa163e541e42-ext\'\nAug 04 03:11:03 s148-72-210-152.secureserver.net nydus-ex[1940]: DEBUG Starting Nydus run-op s148-72-210-152.secureserver.net\nAug 04 03:11:03 s148-72-210-152.secureserver.net nydus-ex[1940]: WARNING Re-connecting to existing store at /opt/nydus/executor/store\nAug 04 03:11:03 s148-72-210-152.secureserver.net nydus-ex[1940]: WARNING Re-connecting to existing queue at /opt/nydus/executor/queue\nAug 04 03:11:03 s148-72-210-152.secureserver.net nydus-ex[1940]: INFO Collecting cpu utilization: [\'sar\', \'-u\', \'1\', \'1\']\nAug 04 03:11:04 s148-72-210-152.secureserver.net nydus-ex[1940]: INFO Collecting memory utilization: cat /proc/meminfo |egrep "^(MemTotal|MemFree|Buffers|Cached|Slab):"\n'}
 
Old 08-04-2019, 01:11 PM   #4
nk96verma@gmail.com
LQ Newbie
 
Registered: Aug 2019
Posts: 4

Original Poster
Rep: Reputation: Disabled
systemctl status named.service Report

Quote:
Originally Posted by scasey View Post
We're going to need a lot more information.
Please post, in code tags, the actual error messages you found in /var/log/messages. In particular, what is giving you the error you quoted?

Also post the result of systemctl status named.service both while things are working and while in a failure.
[root@s148-72-210-152 sswebware]# systemctl status named.service
● named.service - Berkeley Internet Name Domain (DNS)
Loaded: loaded (/usr/lib/systemd/system/named.service; enabled; vendor preset: disabled)
Drop-In: /etc/systemd/system/named.service.d
└─cpanel.conf
Active: active (running) since Sun 2019-08-04 08:25:42 MST; 1h 43min ago
Process: 22433 ExecStop=/bin/sh -c /usr/sbin/rndc stop > /dev/null 2>&1 || /bin/kill -TERM $MAINPID (code=exited, status=0/SUCCESS)
Process: 22446 ExecStart=/usr/sbin/named -u named -c ${NAMEDCONF} $OPTIONS (code=exited, status=0/SUCCESS)
Process: 22444 ExecStartPre=/bin/bash -c if [ ! "$DISABLE_ZONE_CHECKING" == "yes" ]; then /usr/sbin/named-checkconf "$NAMEDCONF"; else echo "Checking of zone files is disabled"; fi (code=exited, status=0/SUCCESS)
Main PID: 22448 (named)
CGroup: /system.slice/named.service
└─22448 /usr/sbin/named -u named -c /etc/named.conf

Aug 04 08:25:42 s148-72-210-152.secureserver.net named[22448]: automatic empty zone: view internal: 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
Aug 04 08:25:42 s148-72-210-152.secureserver.net named[22448]: automatic empty zone: view internal: D.F.IP6.ARPA
Aug 04 08:25:42 s148-72-210-152.secureserver.net named[22448]: automatic empty zone: view internal: 8.E.F.IP6.ARPA
Aug 04 08:25:42 s148-72-210-152.secureserver.net named[22448]: automatic empty zone: view internal: 9.E.F.IP6.ARPA
Aug 04 08:25:42 s148-72-210-152.secureserver.net named[22448]: automatic empty zone: view internal: A.E.F.IP6.ARPA
Aug 04 08:25:42 s148-72-210-152.secureserver.net named[22448]: automatic empty zone: view internal: B.E.F.IP6.ARPA
Aug 04 08:25:42 s148-72-210-152.secureserver.net named[22448]: automatic empty zone: view internal: 8.B.D.0.1.0.0.2.IP6.ARPA
Aug 04 08:25:42 s148-72-210-152.secureserver.net named[22448]: set up managed keys zone for view external, file '3c4623849a49a53911c4a3e48d8cead8a1858960bccdea7a1b978d73ec2f06d7.mkeys'
Aug 04 08:25:42 s148-72-210-152.secureserver.net named[22448]: command channel listening on 127.0.0.1#953
Aug 04 08:25:42 s148-72-210-152.secureserver.net systemd[1]: Started Berkeley Internet Name Domain (DNS).
 
Old 08-04-2019, 03:14 PM   #5
scasey
LQ Veteran
 
Registered: Feb 2013
Location: Tucson, AZ, USA
Distribution: CentOS 7.8.2003
Posts: 5,475

Rep: Reputation: 2100Reputation: 2100Reputation: 2100Reputation: 2100Reputation: 2100Reputation: 2100Reputation: 2100Reputation: 2100Reputation: 2100Reputation: 2100Reputation: 2100
please use [code] tags when posting output. You can edit your previous posts to add them.

It appears that your named configuration is not correct. Did you set that up yourself?
 
Old 08-04-2019, 03:59 PM   #6
nk96verma@gmail.com
LQ Newbie
 
Registered: Aug 2019
Posts: 4

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by scasey View Post
please use [code] tags when posting output. You can edit your previous posts to add them.

It appears that your named configuration is not correct. Did you set that up yourself?
No it is default in GoDaddy vps server .i havent done any changes ,i am facing this issues since last week only before that it was working fine
 
Old 08-04-2019, 04:12 PM   #7
scasey
LQ Veteran
 
Registered: Feb 2013
Location: Tucson, AZ, USA
Distribution: CentOS 7.8.2003
Posts: 5,475

Rep: Reputation: 2100Reputation: 2100Reputation: 2100Reputation: 2100Reputation: 2100Reputation: 2100Reputation: 2100Reputation: 2100Reputation: 2100Reputation: 2100Reputation: 2100
Then you should probably contact godaddy support if you’re using a default configuration that’s not working.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
The "named" service failed to start suryansh Linux - Newbie 2 04-22-2019 03:47 PM
(bind) named: couldn't open pid file '/var/run/named/named.pid' - any help? samengr Linux - Server 6 04-01-2009 07:22 AM
file /var/lib/named/var/named/reverse/named.zero failed: file not found Toadman Linux - Software 15 03-18-2009 08:01 PM
service named cant start error in named.conf file gayanasa Linux - Server 2 07-02-2008 10:58 AM
chown -R named:named /var/named crash the system? joangopan Fedora 2 09-09-2007 03:46 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 07:40 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration