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.

Named Issue

Discussion in 'General Discussion' started by sqnwk, May 23, 2005.

  1. sqnwk

    sqnwk Member

    Joined:
    May 13, 2005
    Messages:
    5
    Likes Received:
    0
    Trophy Points:
    1
    I was adding few accounts and then the sites stopped showing up, I tried rebooting the server, and tried restarting bind. Here is the error I'm getting

    named has failed, please contact the sysadmin (result was "named is not running").

    I'm using WHM 10.1.0 cPanel 10.2.0-R82 with FreeBSD 5.4

    Anyone have any suggestions?
     
  2. LJNS

    LJNS Registered

    Joined:
    May 23, 2005
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    1
    Well I would do 1 of these 3
    1. Sit and wait and hope it works
    2. Contact who ever owns the server
    3. Keep rebooting the server

    I haven't had that problem but sometimes gotta just wait or just keep rebooting.
     
  3. nerdzoll

    nerdzoll Well-Known Member

    Joined:
    Oct 4, 2004
    Messages:
    105
    Likes Received:
    0
    Trophy Points:
    16
    bind

    hey man...
    had the same problem when I first got a server... Try setting up the nameserver through WHM again and that should fix the issue... (cant quitre remember but I think the exact tab is Set Up Nameserver).

    Let me know what happens
    Nerdzoll
     
  4. chirpy

    chirpy Well-Known Member

    Joined:
    Jun 15, 2002
    Messages:
    13,475
    Likes Received:
    20
    Trophy Points:
    38
    Location:
    Go on, have a guess
    If named isn't starting up, have a search on the forums, the various fixes have been discussed in detail many times.
     
  5. gmagana

    gmagana Active Member

    Joined:
    May 18, 2005
    Messages:
    41
    Likes Received:
    0
    Trophy Points:
    6
    First try this:

    - Open an SSH/telnet consoel and log into your server.

    - Trace the output of the named process:
    Code:
    tail -f /var/log/messages | grep named
    Now try to restart BIND/named and watch the log output on the console.

    Usually named will refuse to start if there is an error of a certain severity. For example, I just had named fail to start because I forgot to add a domain's master server IP to the config of the slave server for the domain. BIND/Named refused to start and the reason was stated quite clearly in the system log.

    Anyway, it's a place to start.
     
Loading...

Share This Page