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

Thread: ndc: connect: connection refused

  1. #1
    Member
    Join Date
    Jan 2002
    Posts
    160

    Default ndc: connect: connection refused

    I get this error message when trying to upadate a DNS zone. Any ideas?

  2. #2
    Member
    Join Date
    Aug 2001
    Posts
    75

    Default

    RUn the following commands:

    ndc reload
    tail /var/log/messages

    This should tell you where the error is
    Marc Wyss - marc@mchost.com
    MCHost Inc. - Experts in Private Label Reseller Plans
    http://www.mchost.com

  3. #3
    fh
    fh is offline
    Registered User
    Join Date
    Sep 2001
    Posts
    2

    Default NDC

    Check teh rndckeys are the same in named.conf and rndc.conf. Then ./ndc stop ./ndc start

  4. #4
    fh
    fh is offline
    Registered User
    Join Date
    Sep 2001
    Posts
    2

    Default NDC

    Check the rndckeys are the same in named.conf and rndc.conf. Then ./ndc stop ./ndc start

  5. #5
    Member
    Join Date
    Nov 2001
    Posts
    122

    Default

    Just run

    /scripts/fixndc

    That should get your problem solved fast and easy in most cases.

    Hedgy

  6. #6
    Member
    Join Date
    Jan 2002
    Posts
    13

    Default

    The thinginnabob is that You have bind 9.x but WHM wants 8.x, so You have to prevent /scripts/rpmup to update to hte new bind and You have to downgrade bind to 8.x

    That\'s what I\'ve done, I\'m not the WHM expert so... :P

  7. #7
    Member
    Join Date
    Jan 2002
    Posts
    160

    Default

    Here is what I get in the var/log/mesages

    Feb 5 23:32:12 localhost named[13431]: starting BIND 9.1.0 -u named
    Feb 5 23:32:12 localhost named[13431]: using 2 CPUs
    Feb 5 23:32:12 localhost named[13433]: loading configuration from \'/etc/named.conf\'
    Feb 5 23:32:12 localhost named[13433]: /etc/named.conf:54: parse error near \'ns1.maxxxhosting.com\'
    Feb 5 23:32:12 localhost named[13433]: loading configuration: failure
    Feb 5 23:32:12 localhost named[13433]: exiting (due to fatal error)
    Feb 5 23:32:12 localhost named: named startup succeeded

    I have 2 servers and I\'m trying to use my main server\'s DNS if that helps in troubleshooting this.

  8. #8
    Member
    Join Date
    Aug 2001
    Location
    Fremont CA
    Posts
    537

    Default

    anyone else got a fix on this? i ran both scripts in /scripts and neither work.....

  9. #9
    Member
    Join Date
    Oct 2001
    Posts
    20

    Default same error

    mine is becuase of this according to the tail /var/log/messages

    Feb 8 10:35:04 localhost proftpd[14953]: localhost.localdomain (127.0.0.1[127.0.0.1]) - FTP login timed out, disconnected.

    The script to fix it did not work, said it was already fixed, would like any ideas on this also

  10. #10
    Member
    Join Date
    Aug 2001
    Posts
    839

    Default

    As mentioned- it's true that in most of these new machines WHManager is still looking for bind 9+.....
    A downgrade to bind 8.2.3 and then a lock on the named binary will keep things stable and working with cpanel/whm until everything is in sync with bind 9.1.0, or whatever the current cpanel-installed version is.

    /scripts/fixndc and those peeps work sometimes, don't get me wrong, but I don't have a rhyme or reason or technical pattern to follow yet. When it doubt downgrade for the time being, to get things working.
    ..............................


    http://www.fastservers.net/

    travis@fastservers.net
    ..............................

  11. #11
    bdraco
    Guest

    Default

    Open your named.conf and fix the error on line 54

    Feb 5 23:32:12 localhost named[13433]: loading configuration from '/etc/named.conf'
    Feb 5 23:32:12 localhost named[13433]: /etc/named.conf:54: parse error near 'ns1.maxxxhosting.com'
    Feb 5 23:32:12 localhost named[13433]: loading configuration: failure


    named-checkconf is your friend

  12. #12
    Member
    Join Date
    Oct 2001
    Posts
    20

    Default hi

    root@localhost [/usr/sbin]# ./named-checkconf
    the default for the 'auth-nxdomain' option is now 'no'
    root@localhost [/usr/sbin]#

    but

    root@localhost [/usr/sbin]# ./ndc start
    ndc: connect: connection refused
    root@localhost [/usr/sbin]#

    still no luck for me :/

  13. #13
    bdraco
    Guest

    Default

    [quote:8e9280a85b][i:8e9280a85b]Originally posted by AmityHosting[/i:8e9280a85b]

    root@localhost [/usr/sbin]# ./named-checkconf
    the default for the 'auth-nxdomain' option is now 'no'
    root@localhost [/usr/sbin]#

    but

    root@localhost [/usr/sbin]# ./ndc start
    ndc: connect: connection refused
    root@localhost [/usr/sbin]#

    still no luck for me :/[/quote:8e9280a85b]

    Restart named in WHM

  14. #14
    Member
    Join Date
    Oct 2001
    Posts
    20

    Default

    Attempting to restart bind
    rndc: connect: connection refused

    bind status
    bind did not return a status report


    bind started ok


    That connection refused thing comes up again :/

  15. #15
    cPanel Test Bitch
    Join Date
    Feb 2002
    Location
    Boston MA
    Posts
    596

    Default

    Make sure the keys are right in both named files. I had a problem with this a few times on my server.

Page 1 of 2 12 LastLast

Similar Threads

  1. ndc: connect failed: connection refused
    By adapter in forum cPanel & WHM Discussions
    Replies: 9
    Last Post: 01-01-2004, 02:45 AM
  2. ndc: connect: connection refused
    By AlaskanWolf in forum cPanel & WHM Discussions
    Replies: 4
    Last Post: 05-13-2002, 05:21 AM
  3. ndc: connect: connection refused
    By haze in forum cPanel & WHM Discussions
    Replies: 1
    Last Post: 03-01-2002, 11:08 PM
  4. ndc: connect: connection refused
    By shazad in forum cPanel & WHM Discussions
    Replies: 1
    Last Post: 09-23-2001, 05:15 AM
  5. ndc: connect: connection refused
    By Bullet in forum cPanel & WHM Discussions
    Replies: 1
    Last Post: 09-05-2001, 07:56 AM