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.

named errors

Discussion in 'General Discussion' started by DigiCrime, Dec 1, 2003.

  1. DigiCrime

    DigiCrime Well-Known Member

    Joined:
    Nov 27, 2002
    Messages:
    399
    Likes Received:
    0
    Trophy Points:
    16
    root@xxxxx [/]# service named restart
    Stopping named: rndc: connection to remote host closed
    This may indicate that the remote server is using an older version of
    the command protocol, this host is not authorized to connect,
    or the key is invalid.

    I already ran /scripts/fixndc didnt help...whats wrong?
     
  2. Duncan

    Duncan Member

    Joined:
    Feb 19, 2003
    Messages:
    22
    Likes Received:
    0
    Trophy Points:
    1
    You should check for any errors in /var/log/messages
    Is it a fresh installed server? If yes, did you run the "Initial Nameserver Setup"?
     
  3. DigiCrime

    DigiCrime Well-Known Member

    Joined:
    Nov 27, 2002
    Messages:
    399
    Likes Received:
    0
    Trophy Points:
    16
    yes new server, i did the initial setup thing

    last few entries

    Dec 1 13:47:51 stlouis04 named[5317]: using 1 CPU
    Dec 1 13:47:51 stlouis04 named[5317]: loading configuration from '/etc/named.co
    nf'
    Dec 1 13:47:51 stlouis04 named: named startup succeeded
    Dec 1 13:47:51 stlouis04 named[5317]: no IPv6 interfaces found
    Dec 1 13:47:51 stlouis04 named[5317]: listening on IPv4 interface lo, 127.0.0.1
    #53
    Dec 1 13:47:51 stlouis04 named[5317]: listening on IPv4 interface eth0, xxxxxxx#53
    Dec 1 13:47:51 stlouis04 named[5317]: listening on IPv4 interface eth0:0, xxxxxxxxx#53
    Dec 1 13:47:51 stlouis04 named[5317]: listening on IPv4 interface eth0:1, xxxxxxxxx#53
    Dec 1 13:47:51 stlouis04 named[5317]: listening on IPv4 interface eth0:2, xxxxxxxxx#53
    Dec 1 13:47:51 stlouis04 named[5317]: listening on IPv4 interface eth0:3, xxxxxxxxx#53
    Dec 1 13:47:51 stlouis04 named[5317]: /etc/named.conf:25: couldn't find key 'rn
    dckey' for use with command channel 127.0.0.1#953
    Dec 1 13:47:51 stlouis04 named[5317]: command channel listening on 127.0.0.1#95
    3
    Dec 1 13:47:51 stlouis04 named[5317]: zone 0.0.127.in-addr.arpa/IN: loaded seri
    al 1997022700
    Dec 1 13:47:51 stlouis04 named[5317]: zone xxxxxxxxx/IN: loaded serial 20031
    20100
    Dec 1 13:47:51 stlouis04 named[5317]: dns_master_load: /var/named/xxxxxxxxx.db:3: no current owner name
    Dec 1 13:47:51 stlouis04 named[5317]: zone xxxxxxxxx/IN: loading mas
    ter file /var/named/xxxxxxxxx.db: no owner
    Dec 1 13:47:51 stlouis04 named[5317]: zone localhost/IN: loaded serial 42
    Dec 1 13:47:51 stlouis04 named[5317]: running
    Dec 1 13:47:51 stlouis04 named[5317]: zone xxxxxxxxx/IN: sending notifies (s
    erial 2003120100)
    Dec 1 13:48:02 stlouis04 named[5317]: invalid command from 127.0.0.1#36004: bad
    auth
    Dec 1 13:48:02 stlouis04 named[5317]: shutting down
    Dec 1 13:48:02 stlouis04 named[5317]: stopping command channel on 127.0.0.1#953
    Dec 1 13:48:02 stlouis04 named[5317]: no longer listening on 127.0.0.1#53
    Dec 1 13:48:02 stlouis04 named[5317]: no longer listening on 69.93.7.194#53
    Dec 1 13:48:02 stlouis04 named[5317]: no longer listening on 69.93.7.195#53
    Dec 1 13:48:02 stlouis04 named[5317]: no longer listening on 69.93.7.196#53
    Dec 1 13:48:02 stlouis04 named[5317]: no longer listening on 69.93.7.197#53
    Dec 1 13:48:02 stlouis04 named[5317]: no longer listening on 69.93.7.198#53
    Dec 1 13:48:02 stlouis04 named[5317]: exiting
    Dec 1 13:48:02 stlouis04 named: named shutdown succeeded
     
  4. Duncan

    Duncan Member

    Joined:
    Feb 19, 2003
    Messages:
    22
    Likes Received:
    0
    Trophy Points:
    1
    Hm,
    I would have recommended running /scripts/fixndc as well in such a case.
    Maybe check if you have any instances of named still running and make sure to stop and start it instead of trying to restart it:

    /etc/init.d/named stop
    /etc/init.d/named start

    ...if it still won't start, then you should check the /etc/named.conf file for any bad entries.
     
  5. DigiCrime

    DigiCrime Well-Known Member

    Joined:
    Nov 27, 2002
    Messages:
    399
    Likes Received:
    0
    Trophy Points:
    16
    welp none of these worked sorry

    But I did do this

    vi /etc/named.conf
    find all instances of rndc-key and change to rndckey

    did fixndc and now it restarts and works just fine, although still when i clikc on managed nameserver IPs it takes a while to load the right hand pane
     
Loading...

Share This Page