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.

Error reloading bind on server1: rndc: connect failed: connection refused

Discussion in 'Bind / DNS / Nameserver Issues' started by alrock, Dec 8, 2004.

  1. alrock

    alrock Active Member

    Joined:
    May 31, 2004
    Messages:
    34
    Likes Received:
    0
    Trophy Points:
    6
    When attempting to add an A entry for the hostname, this is the error I get:

    Error reloading bind on server1: rndc: connect failed: connection refused

    None of the available fixes work.

    I tried:

    cd /scripts
    ./updatenow
    ./fixndc

    Twice. It did not work. So I tried:

    cd /scripts
    ./upcp --force

    It did not work either.

    I verified that the 'rndc' key file existed.

    Restarted the server. Still not working.

    I am at a loss. This is the second freshly loaded Cpanel server in the last day that has had this problem. The other one I fixed by manually adding the hostname to the named.conf file. That did not work with this server and I am out of ideas.
     
  2. sawbuck

    sawbuck Well-Known Member

    Joined:
    Jan 18, 2004
    Messages:
    1,367
    Likes Received:
    5
    Trophy Points:
    38
    cPanel Access Level:
    Root Administrator
    Would try running:
    /scripts/fixnamed
    /scripts/fixndc
    /scripts/fixndc

    What OS?
     
  3. alrock

    alrock Active Member

    Joined:
    May 31, 2004
    Messages:
    34
    Likes Received:
    0
    Trophy Points:
    6
    I already tried those fixes, as I stated. They did not work.

    I am running CentOs 3.3
     
  4. sawbuck

    sawbuck Well-Known Member

    Joined:
    Jan 18, 2004
    Messages:
    1,367
    Likes Received:
    5
    Trophy Points:
    38
    cPanel Access Level:
    Root Administrator
    See that you got it solved at WHT. Have pasted that info here for someone else to use.

    Here is the first portion of named.conf

    // generated by named-bootconf.pl

    options {
    directory "/var/named";
    /*
    * If there is a firewall between you and nameservers you want
    * to talk to, you might need to uncomment the query-source
    * directive below. Previous versions of BIND always asked
    * questions using port 53, but BIND 8.1 uses an unprivileged
    * port by default.
    */
    // query-source address * port 53;
    };

    //
    // a caching only nameserver config
    //
    controls {
    inet 127.0.0.1 allow { localhost; } keys { rndckey; };
    };
    zone "." IN {
    type hint;
    file "/var/named/named.ca";
    };

    zone "localhost" IN {
    type master;
    file "/var/named/localhost.zone";
    allow-update { none; };
    };

    zone "0.0.127.in-addr.arpa" IN {
    type master;
    file "/var/named/named.local";
    allow-update { none; };
    };



    Make a backup
    cp /etc/named.conf /etc/named.conf-old

    Open it up and take this out

    controls {
    inet 127.0.0.1 allow { localhost; } keys { rndckey; };
    };

    save it, then type

    service named restart

    then run /scripts/fixndc

    see if that helps

    also make sure it has the right permissions sometimes cpanel mucks that up example

    -rw-r--r-- 1 root root 22037 Dec 8 20:00 /etc/named.conf
     
  5. alrock

    alrock Active Member

    Joined:
    May 31, 2004
    Messages:
    34
    Likes Received:
    0
    Trophy Points:
    6
    Yup. That worked like a charm. Credit to Digicrime for that! :)
     
  6. xWho

    xWho Well-Known Member

    Joined:
    Apr 23, 2003
    Messages:
    112
    Likes Received:
    0
    Trophy Points:
    16
    This method did not fix my occurance of this problem.

    Fedora Core 2. " rndc: connect failed: connection refused " every time I try to create new accounts, make dns changes, etc...

     
  7. nitroburn

    nitroburn Registered

    Joined:
    Dec 8, 2004
    Messages:
    1
    Likes Received:
    0
    Trophy Points:
    1
    I too have the same thing, have never been able to fix it
    Fedora core 2 also

    tryed all stated methods ive seen.

    another thing is in the /var/log/messages there is

    Feb 14 00:36:40 ds named[16716]: couldn't add command channel 127.0.0.1#953: not found
    Feb 14 00:36:40 ds named[16716]: couldn't add command channel ::1#953: not found
    Feb 14 00:36:40 ds named[16716]: running
    Feb 13 16:36:40 ds named: named startup succeeded

    ---
    FOUND THE FIX!!
    Looks like cpanel is managing the chroot'ed named wrong.

    http://www.fedoraforum.org/forum/archive/index.php/t-2998.html

    after the symlinks and editing the empty files in /var/named/chroot it worked.

    ##BEFORE##
    root@ds [/scripts]# service named restart
    Stopping named: rndc: connect failed: connection refused
    [ OK ]
    Starting named: [ OK ]

    ##AFTER##
    root@ds [/scripts]# service named restart
    Stopping named: [ OK ]
    Starting named: [ OK ]
    root@ds [/scripts]#
     
    #7 nitroburn, Feb 13, 2005
    Last edited: Feb 13, 2005
  8. Apocalyptic

    Apocalyptic Member

    Joined:
    Apr 17, 2005
    Messages:
    7
    Likes Received:
    0
    Trophy Points:
    1
    This seems to be dup thread or something, but to get a reply, I'll dup my reply.........sorry :confused:
    I see a lot of same type problems accross the net and always points back to "Cpanel/WHM.
    Shouldn't cPanel put in a fix for this so all people using their software dont have to go to SSH to do a fix?, I mean, isn't that why we use a GUI?, so it will be easier to manage your server.
    This package sure costs enough. If cPanel has corrected this type error, then which release will it be found in, and "IF Not" then "why"
    This was my only holdup, snag, whatever so far using cPanel, and I hope this is the most of it.
    These instructions vary slightly from post to post, and which one is truly correct. I dont want a bunch of headaches, trying this and that till it gets fixed or have to Pay someone to do it after I have paid dearly for this software.
    I appoligize for sounding a little gruff, but I spent my weekend trying to setup the server for my hosting Co. and ofcourse, no tech support from the data center on weekends, less its an emergency, like crashing, then to find that seems to be a cPanel fault.
    How do I get this fixed without having to SSH the server, is their a patch for this problem?
     
  9. chirpy

    chirpy Well-Known Member

    Joined:
    Jun 15, 2002
    Messages:
    13,475
    Likes Received:
    20
    Trophy Points:
    38
    Location:
    Go on, have a guess
    You will have to go to the shell to fix it. Remember that cPanel is not a server management tool, you still have to do that yourself, cPanel is an application that allows you to easily provide web hosting on a server that you maintain. The problem with bind not working is usually down to a faulty installation from the OS vendor. You still need to understand how DNS and bind work to run a DNS name server on the internet.

    If you have a reproducable bug on a particualr OS, then log a bugzilla entry so that cPanel are aware of the problem if one doesn't already exist.
     
  10. AndyReed

    AndyReed Well-Known Member
    PartnerNOC

    Joined:
    May 29, 2004
    Messages:
    2,222
    Likes Received:
    3
    Trophy Points:
    38
    Location:
    Minneapolis, MN
    As Jonathan said, you must SSH to your server and tweak few conf files. If you don't know how, I suggest hiring a sys admin.
     
  11. Apocalyptic

    Apocalyptic Member

    Joined:
    Apr 17, 2005
    Messages:
    7
    Likes Received:
    0
    Trophy Points:
    1
    Well today I learned :) it fixed this problem :D
    funny thing was I mentioned this to people who installed everything, man did they get upset :mad:
     
Loading...

Share This Page