BIND & Named Fail

Discussion in 'Server Operation' started by t471039, Feb 11, 2008.

  1. t471039

    t471039 New Member

    Hi all:

    I am having major problems with BIND and I hope someone can help because I have not been able to find a solution.

    When I tell named to start it says failed. When I look up the status it says named is dead.

    It was working for a long time. Then yesterday it stopped.

    I tried to start and restart named and it says it failed.

    I tried to re-install it from yast and same result.

    I am not sure what to try next, or why it happened and none of my domains are working at this time.

    I am running opensuse 10.2 and I would greatly appreciate any assistance.

    Please let me know if you need more info, I am not sure what info you need. I'll see what other info I can find out.

    Many thanks,
    t
     
  2. topdog

    topdog Active Member HowtoForge Supporter

    Check the logs am sure an error message is being logged to indicate what the problem is.

    Also check the configuration file by running
    Code:
    named-checkconf
    
     
  3. t471039

    t471039 New Member

    Nothing happens when i put in the terminal: named-checkconf

    in var/log/messages:

    Feb 11 10:23:32 named[27018]: starting BIND 9.3.2 -t /var/lib/named -u named
    Feb 11 10:23:32 named[27018]: found 1 CPU, using 1 worker thread
    Feb 11 10:23:32 named[27018]: loading configuration from '/etc/named.conf'
    Feb 11 10:23:32 named[27018]: listening on IPv4 interface lo, 127.0.0.1#53
    Feb 11 10:23:32 named[27018]: listening on IPv4 interface eth0, myIP#53
    Feb 11 10:23:32 named[27018]: loading configuration: empty label
    Feb 11 10:23:32 named[27018]: exiting (due to fatal error)
    Feb 11 10:23:32 startproc: startproc: exit status of parent of /usr/sbin/named: 1

    I am still trying to figure it out at this time. Thanks for the help.
     
  4. t471039

    t471039 New Member

    i am looking on my other server and after the above it normally says:

    command channel listening on 127.0.0.1#953
    command channel listening on ::1#953

    this should appear instead of the error:

    Feb 11 10:23:32 named[27018]: loading configuration: empty label
    Feb 11 10:23:32 named[27018]: exiting (due to fatal error)
    Feb 11 10:23:32 startproc: startproc: exit status of parent of /usr/sbin/named: 1

    any ideas because it dead right now. is there a way to salvage the server?
     
  5. t471039

    t471039 New Member

Share This Page