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.

Fatal, neither ndc or rndc was found on this server (host.domain.com).

Discussion in 'General Discussion' started by gopederick, Oct 21, 2004.

  1. gopederick

    gopederick Active Member

    Joined:
    Nov 11, 2003
    Messages:
    26
    Likes Received:
    0
    Trophy Points:
    151
    What does this mean and how can I get ndc or rndc? I'm running freebsd 5.1
     
    #1 gopederick, Oct 21, 2004
  2. easyhoster1

    easyhoster1 Well-Known Member

    Joined:
    Sep 25, 2003
    Messages:
    659
    Likes Received:
    0
    Trophy Points:
    166
    #2 easyhoster1, Oct 21, 2004
  3. gopederick

    gopederick Active Member

    Joined:
    Nov 11, 2003
    Messages:
    26
    Likes Received:
    0
    Trophy Points:
    151
    I read hrough the whole thread. I can't find what I do after i make deinstall/install bind9. I have freebsd 5.x so i shouldn't have to make a /dev/random because 5.1 doesn't use that anymore. And I can't find any port called rndc-confgen either. Now I'm getting this error

    Error reloading bind on cp1: rndc: neither /etc/namedb/rndc.conf nor /etc/namedb/rndc.key was found Add Complete
     
    #3 gopederick, Oct 21, 2004
  4. gopederick

    gopederick Active Member

    Joined:
    Nov 11, 2003
    Messages:
    26
    Likes Received:
    0
    Trophy Points:
    151
    Ok I've been messing around with it and I finally got it to stop saying "neither /etc/namedb/rndc.conf nor /etc/namedb/rndc.key was found" But after restarting named I get these errors.


    named started ok
    Oct 21 23:29:49 cp1 named[74885]: transfer of 'domain.com/IN' from 192.168.1.1#53: shut down: operation canceled
    Oct 21 23:29:49 cp1 named[74885]: transfer of '0.168.192.in-addr.arpa/IN' from 192.168.1.1#53: shut down: operation canceled
    Oct 21 23:29:49 cp1 named[74885]: exiting
    Oct 21 23:29:49 cp1 named[75008]: starting BIND 9.3.0 -u bind -c /etc/namedb/named.conf
    Oct 21 23:29:49 cp1 named[75008]: couldn't add command channel 127.0.0.1#953: not found
    Oct 21 23:29:49 cp1 named[75008]: couldn't add command channel ::1#953: not found
    Oct 21 23:29:50 cp1 named[75008]: dns_rdata_fromtext: /etc/namedb/gillilandgroup.com.db:15: near eol: unexpected end of input
    Oct 21 23:29:50 cp1 named[75014]: starting BIND 9.3.0 -u bind -c /etc/namedb/named.conf
    Oct 21 23:29:50 cp1 named[75014]: couldn't add command channel 127.0.0.1#953: not found
    Oct 21 23:29:50 cp1 named[75014]: couldn't add command channel ::1#953: not found
    Oct 21 23:29:50 cp1 named[75014]: dns_rdata_fromtext: /etc/namedb/gillilandgroup.com.db:15: near eol: unexpected end of input
    Oct 21 23:29:50 cp1 named[75014]: zone gillilandgroup.com/IN: loading master file /etc/namedb/gillilandgroup.com.db: unexpected end of input
     
    #4 gopederick, Oct 22, 2004
  5. easyhoster1

    easyhoster1 Well-Known Member

    Joined:
    Sep 25, 2003
    Messages:
    659
    Likes Received:
    0
    Trophy Points:
    166
    Looks like your getting there.

    You need to run,

    rndc-confgen -u /dev/urandom

    Then paste the result in the top of your named.conf file.
    If you get a not found error when running rndc-confgen -u /dev/urandom
    you need to reboot and run again.

    Is this the last entry in named.conf ? Make sure to hit enter after };

    should look like;

    zone "domain.com" {
    type master;
    file "/etc/namedb/domain.com.db";
    };
     
    #5 easyhoster1, Oct 22, 2004
  6. gixxerpunk

    gixxerpunk Registered

    Joined:
    Sep 25, 2004
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    151
    I found this to work:

    # rndc-confgen -r /dev/urandom > /etc/namedb/rndc.conf

    This will create a new rndc key (Actually the whole configuration file hence the pipe to a file.

    # rm -f /etc/rndc.conf;ln -s /etc/namedb/rndc.conf /etc/rndc.conf

    Next, remove /etc/rndc.conf if it is there. Then create a symbolic link from /etc/namedb/rndc.conf

    Edit /etc/rndc.conf and /etc/named.conf to both either have rndckey or rndc-key.

    # /scripts/fixndc;/scripts/restartsrv named

    If named restarts with no errors run

    # /scripts/rebuildnamedconf;/scripts/upcp --force;/scripts/restartsrv named

    Hopefully this will help you out.
     
    #6 gixxerpunk, Apr 12, 2005
(You must log in or sign up to post here.)
Loading...
Similar Threads - Fatal neither rndc
  1. Onklmaps

    How to investigate Fatal error

    Onklmaps, Jun 15, 2017, in forum: General Discussion
    Replies:
    3
    Views:
    50
    cPanelMichael
    Jun 16, 2017
  2. Carl Beebe

    SOLVED PHP Fatal Error

    Carl Beebe, Jun 2, 2017, in forum: EasyApache
    Replies:
    4
    Views:
    121
    cPanelMichael
    Jun 5, 2017
  3. liroy

    A fatal error or timeout occurred while processing this directive.

    liroy, May 26, 2017, in forum: Discusión en Español
    Replies:
    1
    Views:
    162
    Infopro
    May 26, 2017
  4. Motamedi

    a fatal error or timeout occurred while processing this directive

    Motamedi, May 17, 2017, in forum: General Discussion
    Replies:
    2
    Views:
    212
    cPanelNick
    May 17, 2017
  5. Paolo.M

    a fatal error or timeout occurred while processing this directive

    Paolo.M, May 10, 2017, in forum: General Discussion
    Replies:
    1
    Views:
    124
    cPanelMichael
    May 10, 2017

Share This Page