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.

Name resolution dying?

Discussion in 'General Discussion' started by AntiAlias, Apr 25, 2004.

  1. AntiAlias

    AntiAlias Registered

    Joined:
    Apr 21, 2004
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    1
    I seem to be having a problem with my cpanel/whm server.

    Approximately every 24 hours, sometimes a bit more name resolution seems to be dying.

    ie. mydomain.com no longer works but i can still access the server fine by its IP address. This also happens to all ports (ie pop3, whm, cpanel etc).

    I can fix it by rebooting the server, but that is something i do not have to do regularly and something i should not have to do recently.

    The server is running an up to date copy of Cpanel ( WHM 9.2.0 cPanel 9.2.0-R24 RedHat 9 - WHM X v2.1.2). Plain with no modifications except for settings and changes made in WHM.

    the BIND DNS service (named) is still running:
    root@bunchie [~]# service named status
    number of zones: 48
    debug level: 0
    xfers running: 0
    xfers deferred: 0
    soa queries in progress: 0
    query logging is OFF
    server is up and running

    Restarting it does not solve the problem.

    Other services such as xinetd, httpd, cpanel, sendmail etc are all still working (as above, i said i could still access the server by its IP).

    Anyone got any ideas whats wrong and what could be causing this?

    Thanks
    ~ Chris
     
  2. Chops2001

    Chops2001 Registered

    Joined:
    Apr 1, 2004
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    1
    same for me... but i dont have SSH access so i cant even reboot!
     
  3. Chops2001

    Chops2001 Registered

    Joined:
    Apr 1, 2004
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    1
    *bump*

    any ideas someone?
     
  4. eth00

    eth00 Well-Known Member
    PartnerNOC

    Joined:
    Mar 30, 2003
    Messages:
    723
    Likes Received:
    1
    Trophy Points:
    18
    Location:
    NC
    cPanel Access Level:
    Root Administrator
    Have you looked in

    /var/log/messages

    also check if dns itself is working
    dig mydomain.com @localhost
     
  5. AntiAlias

    AntiAlias Registered

    Joined:
    Apr 21, 2004
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    1
    After searching through 44,000 lines there is nothing really out of the ordinary there.

    Yes, DNS is working fine and so does running 'dig'.. It returns the expected results for each domain on the server.

    I am really clueless about this one. :confused:
     
  6. eth00

    eth00 Well-Known Member
    PartnerNOC

    Joined:
    Mar 30, 2003
    Messages:
    723
    Likes Received:
    1
    Trophy Points:
    18
    Location:
    NC
    cPanel Access Level:
    Root Administrator
    Are you the only one that has trouble when it goes "down" maybe you are triggering something on your firewall?

    Did you try running the dig when you thought the site was down?

    How about going to dnsstuff.com and having it resolve when the site was down?

    If those do not work try to run
    #telnet localhost 53
    just to see if you can connect to the named port.

    Hopefully one of those will yield some sort of clue or something to work with.
     
  7. AntiAlias

    AntiAlias Registered

    Joined:
    Apr 21, 2004
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    1
    Like i said before, its not the actual process 'named' because it is still running and restarting doesnt fix it.

    I've had a deeper look and i have discovered /var/named/named.ca was alot different to the one stored on my old hard drive (before this server was hacked). I have restored a copy of the old one however i cannot test it because it only appears to be happening when DNS zones are updating with the 'master' server (internic). This explains why it only happens like every 24 hours.

    Hopefully this is the issue and hopefully this will fix it.

    Thanks for the advice though,
    ~ Chris
     
Loading...

Share This Page