I searched everywhere in this forum and have tried all advice, but nameserver simply wouldn't work.
Under WHM status, our VPS shows BIND (named) as working but the domains hosted on the VPS simply wont resolve properly, returning:
Searching for mediacatch.uni.cc A record at h.root-servers.net Got referral to d3.nstld.com. [took 10 ms]
Searching for mediacatch.uni.cc A record at d3.nstld.com. Got referral to NS2.CYLARCOM.NET. [took 76 ms]
[Had to look up A record for NS2.CYLARCOM.NET.; assume 200ms]
Searching for mediacatch.uni.cc A record at NS2.CYLARCOM.NET. Got referral to ns1.rtgasia.com. [took 34 ms]
[Had to look up A record for ns1.rtgasia.com.; assume 200ms]
Searching for mediacatch.uni.cc A record at ns1.rtgasia.com. Reports a server failure! [took 46 ms].
Answer:
Unknown (server failure at ns1.rtgasia.com).
Sorry, I could not continue.
Tried restarting named, reinstalling bind libs, upcp, recompile perl, apache, all to no avail.
We are running:
WHM 10.8.0 cPanel 10.9.0-C56
CentOS 4.4 i686 - WHM X v3.1.0
# /scripts/restartsrv named returns:
Waiting for named to restart..............finished.
named 32506 0.0 0.0 38404 3136 ? Ssl 07:54 0:00 /usr/sbin/named -u named
named started ok
Nov 12 07:54:36 viper named[28330]: invalid command from 127.0.0.1#48797: bad auth
Nov 12 07:54:36 viper named[28330]: shutting down
Nov 12 07:54:36 viper named[28330]: stopping command channel on 127.0.0.1#953
Nov 12 07:54:36 viper named[28330]: no longer listening on 127.0.0.1#53
Nov 12 07:54:36 viper named[28330]: no longer listening on 67.159.30.84#53
Nov 12 07:54:36 viper named[28330]: no longer listening on 67.159.4.45#53
Nov 12 07:54:36 viper named[28330]: no longer listening on 67.159.4.54#53
Nov 12 07:54:36 viper named[28330]: no longer listening on 67.159.4.46#53
Nov 12 07:54:36 viper named[28330]: no longer listening on 67.159.4.47#53
Nov 12 07:54:36 viper named[28330]: no longer listening on 67.159.4.48#53
Nov 12 07:54:36 viper named[28330]: no longer listening on 67.159.4.49#53
Nov 12 07:54:36 viper named[28330]: no longer listening on 67.159.4.50#53
Nov 12 07:54:36 viper named[28330]: no longer listening on 67.159.4.51#53
Nov 12 07:54:36 viper named[28330]: no longer listening on 67.159.4.52#53
Nov 12 07:54:36 viper named: named -TERM succeeded
Nov 12 07:54:36 viper named[28330]: no longer listening on 67.159.4.53#53
Nov 12 07:54:36 viper named[28330]: exiting
Nov 12 07:54:36 viper named: succeeded
Nov 12 07:54:37 viper named[32506]: starting BIND 9.2.4 -u named
Nov 12 07:54:37 viper named[32506]: using 2 CPUs
Nov 12 07:54:37 viper named[32506]: loading configuration from '/etc/named.conf'
Nov 12 07:54:37 viper named[32506]: no IPv6 interfaces found
Nov 12 07:54:37 viper named[32506]: listening on IPv4 interface lo, 127.0.0.1#53
Nov 12 07:54:37 viper named[32506]: listening on IPv4 interface venet0:0, 67.159.30.84#53
Nov 12 07:54:37 viper named[32506]: listening on IPv4 interface venet0:1, 67.159.4.45#53
Nov 12 07:54:37 viper named[32506]: listening on IPv4 interface venet0:10, 67.159.4.54#53
Nov 12 07:54:37 viper named[32506]: listening on IPv4 interface venet0:2, 67.159.4.46#53
Nov 12 07:54:37 viper named[32506]: listening on IPv4 interface venet0:3, 67.159.4.47#53
Nov 12 07:54:37 viper named[32506]: listening on IPv4 interface venet0:4, 67.159.4.48#53
Nov 12 07:54:37 viper named[32506]: listening on IPv4 interface venet0:5, 67.159.4.49#53
Nov 12 07:54:37 viper named[32506]: listening on IPv4 interface venet0:6, 67.159.4.50#53
Nov 12 07:54:37 viper named[32506]: listening on IPv4 interface venet0:7, 67.159.4.51#53
Nov 12 07:54:37 viper named[32506]: listening on IPv4 interface venet0:8, 67.159.4.52#53
Nov 12 07:54:37 viper named[32506]: listening on IPv4 interface venet0:9, 67.159.4.53#53
Nov 12 07:54:37 viper named[32506]: command channel listening on 127.0.0.1#953
Nov 12 07:54:37 viper named[32506]: zone 0.in-addr.arpa/IN: loaded serial 42
Nov 12 07:54:37 viper named[32506]: zone 0.0.127.in-addr.arpa/IN: loaded serial 1997022700
Nov 12 07:54:37 viper named[32506]: zone 255.in-addr.arpa/IN: loaded serial 42
Nov 12 07:54:37 viper named[32506]: zone 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 1997022700
Nov 12 07:54:37 viper named[32506]: zone localdomain/IN: loaded serial 42
Nov 12 07:54:37 viper named[32506]: zone localhost/IN: loaded serial 42
Nov 12 07:54:37 viper named[32506]: running
Nov 12 07:54:37 viper named: named startup succeeded
Status again shows up but the domains is not resolving unless we reboot the VPS.
Any advise would be greatful.
Under WHM status, our VPS shows BIND (named) as working but the domains hosted on the VPS simply wont resolve properly, returning:
Searching for mediacatch.uni.cc A record at h.root-servers.net Got referral to d3.nstld.com. [took 10 ms]
Searching for mediacatch.uni.cc A record at d3.nstld.com. Got referral to NS2.CYLARCOM.NET. [took 76 ms]
[Had to look up A record for NS2.CYLARCOM.NET.; assume 200ms]
Searching for mediacatch.uni.cc A record at NS2.CYLARCOM.NET. Got referral to ns1.rtgasia.com. [took 34 ms]
[Had to look up A record for ns1.rtgasia.com.; assume 200ms]
Searching for mediacatch.uni.cc A record at ns1.rtgasia.com. Reports a server failure! [took 46 ms].
Answer:
Unknown (server failure at ns1.rtgasia.com).
Sorry, I could not continue.
Tried restarting named, reinstalling bind libs, upcp, recompile perl, apache, all to no avail.
We are running:
WHM 10.8.0 cPanel 10.9.0-C56
CentOS 4.4 i686 - WHM X v3.1.0
# /scripts/restartsrv named returns:
Waiting for named to restart..............finished.
named 32506 0.0 0.0 38404 3136 ? Ssl 07:54 0:00 /usr/sbin/named -u named
named started ok
Nov 12 07:54:36 viper named[28330]: invalid command from 127.0.0.1#48797: bad auth
Nov 12 07:54:36 viper named[28330]: shutting down
Nov 12 07:54:36 viper named[28330]: stopping command channel on 127.0.0.1#953
Nov 12 07:54:36 viper named[28330]: no longer listening on 127.0.0.1#53
Nov 12 07:54:36 viper named[28330]: no longer listening on 67.159.30.84#53
Nov 12 07:54:36 viper named[28330]: no longer listening on 67.159.4.45#53
Nov 12 07:54:36 viper named[28330]: no longer listening on 67.159.4.54#53
Nov 12 07:54:36 viper named[28330]: no longer listening on 67.159.4.46#53
Nov 12 07:54:36 viper named[28330]: no longer listening on 67.159.4.47#53
Nov 12 07:54:36 viper named[28330]: no longer listening on 67.159.4.48#53
Nov 12 07:54:36 viper named[28330]: no longer listening on 67.159.4.49#53
Nov 12 07:54:36 viper named[28330]: no longer listening on 67.159.4.50#53
Nov 12 07:54:36 viper named[28330]: no longer listening on 67.159.4.51#53
Nov 12 07:54:36 viper named[28330]: no longer listening on 67.159.4.52#53
Nov 12 07:54:36 viper named: named -TERM succeeded
Nov 12 07:54:36 viper named[28330]: no longer listening on 67.159.4.53#53
Nov 12 07:54:36 viper named[28330]: exiting
Nov 12 07:54:36 viper named: succeeded
Nov 12 07:54:37 viper named[32506]: starting BIND 9.2.4 -u named
Nov 12 07:54:37 viper named[32506]: using 2 CPUs
Nov 12 07:54:37 viper named[32506]: loading configuration from '/etc/named.conf'
Nov 12 07:54:37 viper named[32506]: no IPv6 interfaces found
Nov 12 07:54:37 viper named[32506]: listening on IPv4 interface lo, 127.0.0.1#53
Nov 12 07:54:37 viper named[32506]: listening on IPv4 interface venet0:0, 67.159.30.84#53
Nov 12 07:54:37 viper named[32506]: listening on IPv4 interface venet0:1, 67.159.4.45#53
Nov 12 07:54:37 viper named[32506]: listening on IPv4 interface venet0:10, 67.159.4.54#53
Nov 12 07:54:37 viper named[32506]: listening on IPv4 interface venet0:2, 67.159.4.46#53
Nov 12 07:54:37 viper named[32506]: listening on IPv4 interface venet0:3, 67.159.4.47#53
Nov 12 07:54:37 viper named[32506]: listening on IPv4 interface venet0:4, 67.159.4.48#53
Nov 12 07:54:37 viper named[32506]: listening on IPv4 interface venet0:5, 67.159.4.49#53
Nov 12 07:54:37 viper named[32506]: listening on IPv4 interface venet0:6, 67.159.4.50#53
Nov 12 07:54:37 viper named[32506]: listening on IPv4 interface venet0:7, 67.159.4.51#53
Nov 12 07:54:37 viper named[32506]: listening on IPv4 interface venet0:8, 67.159.4.52#53
Nov 12 07:54:37 viper named[32506]: listening on IPv4 interface venet0:9, 67.159.4.53#53
Nov 12 07:54:37 viper named[32506]: command channel listening on 127.0.0.1#953
Nov 12 07:54:37 viper named[32506]: zone 0.in-addr.arpa/IN: loaded serial 42
Nov 12 07:54:37 viper named[32506]: zone 0.0.127.in-addr.arpa/IN: loaded serial 1997022700
Nov 12 07:54:37 viper named[32506]: zone 255.in-addr.arpa/IN: loaded serial 42
Nov 12 07:54:37 viper named[32506]: zone 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 1997022700
Nov 12 07:54:37 viper named[32506]: zone localdomain/IN: loaded serial 42
Nov 12 07:54:37 viper named[32506]: zone localhost/IN: loaded serial 42
Nov 12 07:54:37 viper named[32506]: running
Nov 12 07:54:37 viper named: named startup succeeded
Status again shows up but the domains is not resolving unless we reboot the VPS.
Any advise would be greatful.