Page 1 of 2 12 LastLast
Results 1 to 15 of 24

Thread: rndc: no server specified and no default

  1. #1
    Registered Member
    Join Date
    Feb 2003
    Posts
    128

    Default rndc: no server specified and no default

    i am getting this error after i rebooted my freebsd 4.9 machine:

    Code:
    rndc: neither /etc/namedb/rndc.conf nor /etc/namedb/rndc.key was found
    not sure whats going on. i read for some other ndc problems there was a script that fixed them. so i ran /scripts/fixndc and here was the output:

    Code:
    su-2.05b# /scripts/fixndc
    Found controls in named.conf ..
    Adding key...
    Restarting bind.....Waiting for named to restart..............finished.
    
    rndc: no server specified and no default
    
    named started ok
    Jul 14 22:43:08 backstow named[86939]: starting BIND 9.2.3 -u bind -c /etc/namedb/named.conf
    Jul 14 22:43:08 backstow named[86939]: none:0: open: /etc/namedb/rndc.key: file not found
    Jul 14 22:43:08 backstow named[86939]: /etc/namedb/named.conf:6: couldn't install keys for command channel 127.0.0.1#953: file not found
    Jul 14 22:43:08 backstow named[86939]: /etc/namedb/named.conf:6: couldn't add command channel 127.0.0.1#953: file not found
    Jul 14 22:43:08 backstow named[86939]: couldn't open pid file '/var/run/named.pid': File exists
    Jul 14 22:43:08 backstow named[86939]: exiting (due to early fatal error)
    Done
    All fixed
    su-2.05b#
    now everytime i try to use ndc to reload or restart bind i get this error:

    Code:
    rndc: no server specified and no default
    not sure whats goin on or why those files dont exist =\

    could anyone help me out?

  2. #2
    Registered Member
    Join Date
    Sep 2003
    Location
    UK, Luton
    Posts
    197

    Default

    I have the exact same problem, on one of the machines named is unable to start, the others are working purely because the machine and named havnt restarted since what ever has made this change.
    Regards,
    James Smith
    UH Hosting Ltd

  3. #3
    Registered Member
    Join Date
    Feb 2003
    Posts
    128

    Default

    this problem was solved by my license provider support. i do not know what the exact solution was. sorry.

  4. #4
    Registered Member
    Join Date
    Sep 2003
    Location
    UK, Luton
    Posts
    197

    Default

    Got it sorted anyway

    Overriding problem came from bind being unable to make the pid file in /var/run after updating to bind9.
    Regards,
    James Smith
    UH Hosting Ltd

  5. #5
    Registered Member
    Join Date
    Apr 2003
    Posts
    6

    Default

    We are having the same problem- what is the solution?

  6. #6
    Registered Member
    Join Date
    Sep 2003
    Location
    UK, Luton
    Posts
    197

    Default

    Change permissions on /var/run so bind can create the pid file.
    Regards,
    James Smith
    UH Hosting Ltd

  7. #7
    Registered Member
    Join Date
    May 2004
    Location
    Aggieland, TX
    Posts
    15

    Default

    I attempted to change the permissions (to 766) on /var/run and that did not fix this same exact problem for me. I'm currently having the tech support team look into this for me, but what's really weird about this is the fact that my RNDC key randomly got deleted. I doubt it was a hack of any sort, because plenty more files would be gone in that case, but I am totally stumped. I don't know if recreating the key will fix the problem or not, but reinstalling the BIND9 port did not fix the issue.
    Christoper Weldon
    IT Systems Administrator
    CerberusOnline.com
    cweldon@cerberusonline.com

  8. #8
    Registered Member
    Join Date
    Sep 2003
    Posts
    104

    Default same problem here!!

    Hii,

    what is the solution to this.. I tried to /scritps/fixndc and that didn't work!!. Please help.. This happen when you upgrade to bind 9.2.3 what is going on>?? It doesn't work on all freebsd version.. 4.9 no good 4.10 no good 5.2.1 no good. What is going on. All getting the same error.

    please help!!

  9. #9
    Registered Member
    Join Date
    May 2004
    Location
    Aggieland, TX
    Posts
    15

    Default

    Figured out my problem. The first problem had to deal with incorrect permissions on the /var/run directory. When I did change the permissions to 777, it worked just fine. However, because I don't want an open vulnerability like that, one of the technicians at my host I talked to recommended that I put the following line into my named.conf file:

    Code:
    pid-file "/tmp/named.pid";
    That way, the permissions on the /var/run directory can stay at 744, secured. Also, that goes under the options section! Now, for the RNDC key problem, what I found was that my rndc.conf and rndc.key file were missing. When I run /scripts/fixndc, they create them automatically, but they are completely empty. So, I took the suggestions from other users who had rndc.conf files already in place, and took the rndc.conf.sample file (found in the same directory), copied it to rndc.conf and renamed "key" to "rndckey" each place that it was found. Once I had done that, then I was able to run /scripts/fixndc and it looked like the problem has been solved. The script fixed everything, though the rndc.key file is still empty. Not sure what to do about that, but for the meantime I'm not longer getting errors. Hope this helps.
    Last edited by neraath; 08-01-2004 at 10:40 AM.
    Christoper Weldon
    IT Systems Administrator
    CerberusOnline.com
    cweldon@cerberusonline.com

  10. #10
    Registered Member
    Join Date
    Jan 2004
    Posts
    28

    Default

    I'm very impressed... two steps, problem solved.

    Worked for me, I'm much obliged .

    Thanks,
    J.

  11. #11
    Registered Member
    Join Date
    Apr 2005
    Posts
    12

    Default Fatal, neither ndc or rndc was found on this server

    Fatal, neither ndc or rndc was found on this server

    while naming server or adding new useraccount


    Please any guru with freeBSD experience
    or goodwilling newby like me

    can you please comment and give me advice
    (no dont go tell me to flush it )
    im on this for 3 weeks now before i dared to post here


    Fatal, neither ndc or rndc was found on this server


    running
    WHM 10.1.0 cPanel 10.2.0-R4
    FreeBSD 5.3-RELEASE i386 - WHM X

    this is a fresh new Cpanel install

    and so am i!
    This is how i started this month with my FIRST dedicated woohoo.
    EVER FLEW a jumbo 747 while just learned how to ride a bycycle ?
    this is how this noob/newby feels while crashing down and the console says
    RED RED RED balls but before you tell me search is my best friend please
    have some patience with me, maybe you can explain

    im a total newby and fixed (not completely) this error by reading the forum
    1 moment i had Bind9 working YESYES

    but the
    "Fatal, neither ndc or rndc was found on this server" message always been there
    when i add a new user account

    /scripts/fixndc
    fix nrcd does not work on freeBSD!!
    reading this forum it has been reported a bug and should be
    fixed in the next release, but that was a post of last year???
    anyway i need a solution now offcourse

    this folowing helped with the bind9 part not showing red anymore after
    typing in cp /usr/local/sbin /usr/sbin/named


    did an PTR in-addr.arpa on the shared ip


    generated a new key
    rndc-confgen -u /dev/urandom



    edited the -
    vi named.conf ; nrcd.conf ; nrcd.key (took the - out of nrcd-key)


    set chmod 755 on
    pid-file "/var/tmp/named.pid";


    this is my named.conf

    --------------------------------------
    zone "." {
    type hint;
    file "/var/named/named.ca";
    };







    key "rndckey" {
    algorithm hmac-md5;
    secret "I6kxyblablablaxxxxxxx==";
    };

    controls {
    inet 127.0.0.1 port 953
    allow { 127.0.0.1; } keys { "rndckey"; };
    };


    // $FreeBSD: src/etc/namedb/named.conf,v 1.15.2.1 2004/09/30 23:36:07 dougb Exp
    $
    //
    // Refer to the named.conf(5) and named(8) man pages, and the documentation
    // in /usr/share/doc/bind9 for more details.
    options {
    directory "/etc/namedb";
    pid-file "/var/run/named/pid";
    pid-file "/var/tmp/named.pid";
    dump-file "/var/dump/named_dump.db";
    statistics-file "/var/stats/named.stats";

    };
    zone "1230985.xxl.nut.net" { type master; file "/etc/namedb/1230985.xxl.nut.net.db";
    };

    zone "webhostingdomain.com" { type master; file "/etc/namedb/webhostin
    gdomain.com.db"; };

    zone "111.222.333.44.in-addr.arpa" { type master; file "/etc/namedb/111.222.333.
    44.in-addr.arpa.db"; };

    zone "secondomain.com" {
    type master;
    file "/etc/namedb/secondomain.db";
    };

    -----------------------------------

    then i symlinked


    ls -s /etc/namedb/named.conf /etc/named.conf
    ls -s /etc/namedb/nrcd.conf /etc/nrcd.conf
    ls -s /etc/namedb/nrcd.key /etc/nrcd.key


    it worked for a while and then poof all gone
    this where my first steps in serverland

    can you please give me some suggestions ?
    it worked for 50%, after adding or deleting a user
    the other users are not visible anymory by domainname (only with ip)
    had server status all in the green!
    after gracefull reboot the red balls are back gradually all back green
    except for BIND , keys have not been altered
    im confused and hope you can help



    Them Cuiper aka TC.
    Last edited by nicnicy; 05-16-2005 at 06:54 AM.

  12. #12
    Registered Member
    Join Date
    Sep 2003
    Location
    UK, Luton
    Posts
    197

    Default

    Try sym linking ndc to rndc, had this problem on a few servers after a cPanel update and that resolved it for us:

    ln -s /usr/local/sbin/rndc /usr/sbin/ndc
    Regards,
    James Smith
    UH Hosting Ltd

  13. #13
    Registered Member
    Join Date
    Apr 2005
    Posts
    12

    Thumbs up re symlink rndc to ndc

    YES


    James !!!
    Big thumbs up to you.




    You SOLVED the problem, it was amazing to see all working at once after this line
    Thank you very much for i was real desperate


    Thank You James


    TC
    Last edited by nicnicy; 05-05-2005 at 07:26 AM.

  14. #14
    Registered Member
    Join Date
    Apr 2005
    Posts
    12

    Exclamation Fatal, neither ndc or rndc was found on this server

    posting again about

    Fatal, neither ndc or rndc was found on this server


    running
    WHM 10.1.0 cPanel 10.2.0-R4
    FreeBSD 5.3-RELEASE i386 - WHM X



    TC here back with bad news, the fix is not permanent.



    next day looked at websites Poof gone again seeing the apache templatescreen of the server now


    the message Fatal, neither ndc or rndc was found on this server stayed after the symlink
    but all websites where up at once

    I think i can live with an errormessage if all systems work.
    I do not complaint.
    A goodwilling fellow webmaster comes up with an idea to get back in business
    as a patch for software that suposed to work im thankfull i do not complain
    (pinning the bad holes with bubble gum and keeping it together with shoelace. )


    I hope to get a definite solution, or am i the only noob in the world taking a licence Cpanel on freeBSD5.3 ??? please share me how you solved it, reading back the forumhistory this has anoyed many webmasters in the past.


    TC

  15. #15
    Registered Member
    Join Date
    Sep 2003
    Location
    UK, Luton
    Posts
    197

    Default

    Do you have cPanel set to auto update or manual? Nothing will change unless its doing something, like a upcp or sysup update.

    I would recommend setting this to manual if its on auto, you’re running the risk of things breaking in the night using the auto feature. Would be best to set a maintenance window each week, let your customers know there may be work carried out in that time. Such as cPanel update etc.
    Regards,
    James Smith
    UH Hosting Ltd

Page 1 of 2 12 LastLast

Similar Threads

  1. Replies: 5
    Last Post: 08-31-2012, 03:20 AM
  2. Replies: 5
    Last Post: 10-31-2011, 03:25 AM
  3. rndc: no server specified and no default???
    By Musmand in forum General Discussion
    Replies: 1
    Last Post: 05-29-2005, 07:22 AM
  4. Replies: 5
    Last Post: 04-12-2005, 09:49 PM
  5. rndc Error reloading bind - rndc: get key: not found
    By rodstewart in forum Bind / DNS / Nameserver Issues
    Replies: 5
    Last Post: 05-05-2004, 05:35 PM
bargain