The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

NameServer will only work if we REBOOT

Discussion in 'Bind / DNS / Nameserver Issues' started by brendanrtg, Nov 11, 2006.

  1. brendanrtg

    brendanrtg Well-Known Member

    Joined:
    Oct 4, 2006
    Messages:
    311
    Likes Received:
    0
    Trophy Points:
    16
    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.
     
  2. tanfwc

    tanfwc Well-Known Member

    Joined:
    Mar 12, 2004
    Messages:
    94
    Likes Received:
    0
    Trophy Points:
    6
    Look into the named log file for detail problem. Can paste here so the guys here can assist too :)
     
  3. brianoz

    brianoz Well-Known Member

    Joined:
    Mar 13, 2004
    Messages:
    1,146
    Likes Received:
    6
    Trophy Points:
    38
    Location:
    Melbourne, Australia
    cPanel Access Level:
    Root Administrator
    FYI the named log file is /var/log/messages.

    If you run "tail -f /var/log/messages" in one window and run "service named restart" in another window you'll see any problem messages in the tail window.
     
  4. brendanrtg

    brendanrtg Well-Known Member

    Joined:
    Oct 4, 2006
    Messages:
    311
    Likes Received:
    0
    Trophy Points:
    16
    I did a tail and service named restart, got a long lists but everything seems normal with the exception of the LAME SERVERS being listed which is not of ours and I cant even find the entries under WHM:

    Nov 12 20:04:08 viper named[24271]: running
    Nov 12 20:04:08 viper named: named startup succeeded
    Nov 12 20:04:08 viper named[24271]: zone art.xinfo.us/IN: sending notifies (serial 2006092603)
    Nov 12 20:04:11 viper named[24271]: zone clubfeed.org/IN: sending notifies (serial 2006110703)
    Nov 12 20:04:12 viper named[24271]: zone 1013088.eb.cn/IN: sending notifies (serial 2006093001)
    Nov 12 20:04:12 viper named[24271]: zone cc1069.uni.cc/IN: sending notifies (serial 2006092901)
    Nov 12 20:04:12 viper named[24271]: zone blogmalaysia.info/IN: sending notifies (serial 2006092601)
    Nov 12 20:04:12 viper named[24271]: zone 66she.uni.cc/IN: sending notifies (serial 2006100201)
    Nov 12 20:04:12 viper named[24271]: zone movie.xinfo.us/IN: sending notifies (serial 2006092601)
    Nov 12 20:04:12 viper named[24271]: zone xinfo.us/IN: sending notifies (serial 2006092601)
    Nov 12 20:04:13 viper named[24271]: zone hhj.uunx.com/IN: sending notifies (serial 2006092903)
    Nov 12 20:04:13 viper named[24271]: zone csuchen.be/IN: sending notifies (serial 2006092605)
    Nov 12 20:04:13 viper named[24271]: zone uland.info/IN: sending notifies (serial 2006093001)
    Nov 12 20:04:13 viper named[24271]: zone bbs0.net.ru/IN: sending notifies (serial 2006092901)
    Nov 12 20:04:13 viper named[24271]: zone gyl.uni.cc/IN: sending notifies (serial 2006092901)
    Nov 12 20:04:13 viper named[24271]: zone wapba.com.cn/IN: sending notifies (serial 2006093001)
    Nov 12 20:04:13 viper named[24271]: zone anhhuaanhsemaiyeu.be/IN: sending notifies (serial 2006092603)
    Nov 12 20:04:13 viper named[24271]: zone dome.net.ru/IN: sending notifies (serial 2006092901)
    Nov 12 20:04:13 viper named[24271]: zone yxpk.eb.cn/IN: sending notifies (serial 2006093001)
    Nov 12 20:04:13 viper named[24271]: zone e-goldchina.com.cn/IN: sending notifies (serial 2006110702)
    Nov 12 20:04:13 viper named[24271]: zone mikey.net.ru/IN: sending notifies (serial 2006093001)
    Nov 12 20:04:13 viper named[24271]: zone 5sky.net.ru/IN: sending notifies (serial 2006093001)
    Nov 12 20:04:13 viper named[24271]: zone sweetrevenue.com/IN: sending notifies (serial 2006110704)
    Nov 12 20:04:13 viper named[24271]: zone zoz.xinfo.us/IN: sending notifies (serial 2006092601)
    Nov 12 20:04:13 viper named[24271]: zone rtg.be/IN: sending notifies (serial 2006092601)
    Nov 12 20:04:13 viper named[24271]: zone dy.172w.com/IN: sending notifies (serial 2006092901)
    Nov 12 20:04:13 viper named[24271]: zone demo.mediacatch.uni.cc/IN: sending notifies (serial 2006110901)
    Nov 12 20:04:13 viper named[24271]: zone feedclub.org/IN: sending notifies (serial 2006110703)
    Nov 12 20:04:13 viper named[24271]: zone q8spirit.be/IN: sending notifies (serial 2006100201)
    Nov 12 20:04:13 viper named[24271]: zone wzboy.org.ru/IN: sending notifies (serial 2006093005)
    Nov 12 20:04:13 viper named[24271]: zone 92blog.uni.cc/IN: sending notifies (serial 2006092901)
    Nov 12 20:04:13 viper named[24271]: zone hackpc.uni.cc/IN: sending notifies (serial 2006092901)
    Nov 12 20:04:13 viper named[24271]: zone yxpk.uni.cc/IN: sending notifies (serial 2006100601)
    Nov 12 20:04:13 viper named[24271]: zone ggv.org.ru/IN: sending notifies (serial 2006092901)
    Nov 12 20:04:13 viper named[24271]: zone sppjw.com/IN: sending notifies (serial 2006093001)
    Nov 12 20:04:14 viper named[24271]: zone tt1069.net.ru/IN: sending notifies (serial 2006092901)
    Nov 12 20:04:14 viper named[24271]: zone cnsexer.com/IN: sending notifies (serial 2006092901)
    Nov 12 20:04:14 viper named[24271]: zone yugi-ar.info/IN: sending notifies (serial 2006100201)
    Nov 12 20:04:14 viper named[24271]: zone ggxx8.com/IN: sending notifies (serial 2006110902)
    Nov 12 20:04:14 viper named[24271]: zone leiyu.uni.cc/IN: sending notifies (serial 2006092901)
    Nov 12 20:04:14 viper named[24271]: zone sdcool.net/IN: sending notifies (serial 2006093001)
    Nov 12 20:04:14 viper named[24271]: zone gauso.net.ru/IN: sending notifies (serial 2006092901)
    Nov 12 20:04:14 viper named[24271]: zone hiva.xinfo.us/IN: sending notifies (serial 2006092601)
    Nov 12 20:04:14 viper named[24271]: zone 64.yi.org/IN: sending notifies (serial 2006093001)
    Nov 12 20:04:14 viper named[24271]: zone 769394.uni.cc/IN: sending notifies (serial 2006092901)
    Nov 12 20:04:14 viper named[24271]: zone yhmemory.uni.cc/IN: sending notifies (serial 2006092901)
    Nov 12 20:04:14 viper named[24271]: zone d6sex.com/IN: sending notifies (serial 2006110703)
    Nov 12 20:04:14 viper named[24271]: zone sub.xinfo.us/IN: sending notifies (serial 2006092601)
    Nov 12 20:04:14 viper named[24271]: zone lovefeelings.uni.cc/IN: sending notifies (serial 2006092901)
    Nov 12 20:04:14 viper named[24271]: zone bbs.s1.ons.net.ru/IN: sending notifies (serial 2006093001)
    Nov 12 20:04:14 viper named[24271]: zone q8sad.be/IN: sending notifies (serial 2006100201)
    Nov 12 20:04:14 viper named[24271]: zone free.uunx.com/IN: sending notifies (serial 2006092901)
    Nov 12 20:04:14 viper named[24271]: zone weilansky.uni.cc/IN: sending notifies (serial 2006092901)
    Nov 12 20:04:14 viper named[24271]: zone linbensen.uni.cc/IN: sending notifies (serial 2006092901)
    Nov 12 20:04:14 viper named[24271]: zone dmzy.net.ru/IN: sending notifies (serial 2006092901)
    Nov 12 20:04:14 viper named[24271]: zone 78.yi.org/IN: sending notifies (serial 2006093011)
    Nov 12 20:04:14 viper named[24271]: zone coolfish.be/IN: sending notifies (serial 2006092903)
    Nov 12 20:04:14 viper named[24271]: zone blog.ygdj.net/IN: sending notifies (serial 2006092901)
    Nov 12 20:04:14 viper named[24271]: zone magical-surf.com/IN: sending notifies (serial 2006110702)
    Nov 12 20:04:14 viper named[24271]: zone webhostz.be/IN: sending notifies (serial 2006100201)
    Nov 12 20:04:14 viper named[24271]: zone jspfans.cn/IN: sending notifies (serial 2006100201)
    Nov 12 20:04:14 viper named[24271]: zone 7obey.info/IN: sending notifies (serial 2006100201)
    Nov 12 20:04:14 viper named[24271]: zone soboo.org.ru/IN: sending notifies (serial 2006093007)
    Nov 12 20:04:14 viper named[24271]: zone cuchuoihanoi.com/IN: sending notifies (serial 2006092601)
    Nov 12 20:04:14 viper named[24271]: zone ns1.yohosting.com/IN: sending notifies (serial 2006101601)
    Nov 12 20:04:14 viper named[24271]: zone yohosting.com/IN: sending notifies (serial 2006100201)
    Nov 12 20:04:14 viper named[24271]: zone yoyo8.uni.cc/IN: sending notifies (serial 2006093001)
    Nov 12 20:04:14 viper named[24271]: zone web.losejoy.com/IN: sending notifies (serial 2006093001)
    Nov 12 20:04:14 viper named[24271]: zone vsx.uni.cc/IN: sending notifies (serial 2006093001)
    Nov 12 20:04:14 viper named[24271]: zone bimbim.net/IN: sending notifies (serial 2006092601)
    Nov 12 20:04:14 viper named[24271]: zone xfdtk.com/IN: sending notifies (serial 2006100801)
    Nov 12 20:04:14 viper named[24271]: zone hhj.com/IN: sending notifies (serial 2006092901)
    Nov 12 20:04:14 viper named[24271]: zone cenjay.uni.cc/IN: sending notifies (serial 2006092901)
    Nov 12 20:04:14 viper named[24271]: zone dienmaymanhduc.com/IN: sending notifies (serial 2006100201)
    Nov 12 20:04:14 viper named[24271]: zone hhk.com/IN: sending notifies (serial 2006092901)
    Nov 12 20:04:14 viper named[24271]: zone dbjlck.uni.cc/IN: sending notifies (serial 2006092901)
    Nov 12 20:04:14 viper named[24271]: zone ehozt.info/IN: sending notifies (serial 2006092602)
    Nov 12 20:04:14 viper named[24271]: zone kw7ub.net/IN: sending notifies (serial 2006101402)
    Nov 12 20:04:14 viper named[24271]: zone 108s.uni.cc/IN: sending notifies (serial 2006092901)
    Nov 12 20:04:14 viper named[24271]: zone 8859.be/IN: sending notifies (serial 2006092901)
    Nov 12 20:04:14 viper named[24271]: lame server resolving 'ns1.7log3.com' (in '7log3.com'?): 208.53.165.173#53
    Nov 12 20:04:14 viper named[24271]: lame server resolving 'ns1.7log3.com' (in '7log3.com'?): 66.90.118.207#53
    Nov 12 20:04:14 viper named[24271]: lame server resolving 'ns1.7log3.com' (in '7log3.com'?): 66.90.118.207#53
    Nov 12 20:04:14 viper named[24271]: lame server resolving 'ns1.7log3.com' (in '7log3.com'?): 208.53.165.173#53

    Nov 12 20:04:14 viper named[24271]: received notify for zone 'imse.eu.org'
    Nov 12 20:04:14 viper named[24271]: received notify for zone 'lookatsearch.com'
    Nov 12 20:04:15 viper named[24271]: received notify for zone 'd6sex.com'
    Nov 12 20:04:15 viper named[24271]: received notify for zone 'bluerwebmail.com'
    Nov 12 20:04:15 viper named[24271]: received notify for zone 'green-worlder.com'
    Nov 12 20:04:15 viper named[24271]: received notify for zone '52mm.eu.org'
    Nov 12 20:04:15 viper named[24271]: received notify for zone 'divinityhost.net'
    Nov 12 20:04:16 viper named[24271]: received notify for zone 'e-goldchina.com.cn'
    Nov 12 20:04:18 viper named[24271]: received notify for zone 'staff.mediacatch.uni.cc'
    Nov 12 20:04:18 viper named[24271]: received notify for zone 'mediacatch.uni.cc'
    Nov 12 20:04:18 viper named[24271]: received notify for zone 'oimm.uni.cc'
    Nov 12 20:04:18 viper named[24271]: received notify for zone 'demo.mediacatch.uni.cc'
    Nov 12 20:04:18 viper named[24271]: received notify for zone 'ehozt.info'
    Nov 12 20:04:19 viper named[24271]: received notify for zone 'clubfeed.org'
    Nov 12 20:04:19 viper named[24271]: received notify for zone 'feedclub.org'
    Nov 12 20:04:19 viper named[24271]: received notify for zone 'ggxx8.com'
    Nov 12 20:04:19 viper named[24271]: received notify for zone 'magical-surf.com'
    Nov 12 20:04:21 viper named[24271]: received notify for zone 'searchverve.com'
    Nov 12 20:04:21 viper named[24271]: received notify for zone 'sweetrevenue.com'
    Nov 12 20:04:21 viper named[24271]: received notify for zone 'pkdosonline.com'
     
  5. brianoz

    brianoz Well-Known Member

    Joined:
    Mar 13, 2004
    Messages:
    1,146
    Likes Received:
    6
    Trophy Points:
    38
    Location:
    Melbourne, Australia
    cPanel Access Level:
    Root Administrator
    Looks to me like named is starting up and loading your zones perfectly. It doesn't look like a problem with named unless the problem is specific to one domain, in which case you need to check that domain is being loaded correctly in the above.

    I'd check that your networking is working, for instance, check to see whether it's listening on localhost and then interface by interface with:
    Code:
    host domain.com interface-ip
    You should get an answer giving an IP if it's working and almost nothing or a timeout if it's not.
     
Loading...

Share This Page