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.

bind error

Discussion in 'Bind / DNS / Nameserver Issues' started by ph33r420, Jan 9, 2005.

  1. ph33r420

    ph33r420 Active Member

    Joined:
    Jan 8, 2005
    Messages:
    25
    Likes Received:
    0
    Trophy Points:
    1
    named has failed, please contact the sysadmin (result was "named is not running").
    Jan 9 21:30:06 poweredbyxeon named: named shutdown failed
    Jan 9 21:30:06 poweredbyxeon named[2439]: starting BIND 9.2.1 -u named
    Jan 9 21:30:06 poweredbyxeon named[2439]: using 1 CPU
    Jan 9 21:30:06 poweredbyxeon named[2442]: loading configuration from '/etc/named.conf'
    Jan 9 21:30:06 poweredbyxeon named[2442]: no IPv6 interfaces found
    Jan 9 21:30:06 poweredbyxeon named[2442]: listening on IPv4 interface lo, 127.0.0.1#53
    Jan 9 21:30:06 poweredbyxeon named[2442]: could not listen on UDP socket: shutting down
    Jan 9 21:30:06 poweredbyxeon named[2442]: creating IPv4 interface lo failed; interface ignored
    Jan 9 21:30:06 poweredbyxeon named[2442]: listening on IPv4 interface eth0, 123.123.123.1#53
    Jan 9 21:30:06 poweredbyxeon named[2442]: could not listen on UDP socket: shutting down
    Jan 9 21:30:06 poweredbyxeon named[2442]: creating IPv4 interface eth0 failed; interface ignored
    Jan 9 21:30:06 poweredbyxeon named[2442]: not listening on any interfaces
    Jan 9 21:30:06 poweredbyxeon named[2442]: could not configure root hints from '/etc/namedb/named.ca': file not found
    Jan 9 21:30:06 poweredbyxeon named[2442]: loading configuration: file not found
    Jan 9 21:30:06 poweredbyxeon named[2442]: exiting (due to fatal error)
    Jan 9 21:30:06 poweredbyxeon named: named shutdown succeeded




    first time i tried to start bind. should i make /etc/namedb or edit named.conf to look for named.ca in /etc?


    also, what is happening with this error could not listen on UDP socket: shutting down
    ?
     
  2. Blue|Fusion

    Blue|Fusion Well-Known Member

    Joined:
    Sep 12, 2004
    Messages:
    378
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Cleveland, Ohio
    /scripts/fixndc
    /scripts/fixnamed

    And for UDP port problem, it looks like port 53/UDP is blocked or eth0 is incorrectly bound to IP.
     
  3. furquan

    furquan Well-Known Member

    Joined:
    Jul 27, 2002
    Messages:
    425
    Likes Received:
    0
    Trophy Points:
    16
    Hi

    I am also facing the sane problem :-

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

    Tried :-

    /scripts/fixndc
    /scripts/upcp --force
    /scripts/upcp
    /scripts/fixnamed

    Checked logs :- tail -f /var/log/messages ( nothing here either )

    Restarted the server too. but all in vein :(

    Can some one assist ?

    thanks
     
  4. onestepback

    onestepback Registered

    Joined:
    Jan 9, 2005
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    1
    I defined my named.ca file in /etc/named.conf as /var/named/named.ca


    just search for named.ca

    make sure the path is correct.
     
Loading...

Share This Page