1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

unable to start named- loading configuration: bad base64 encoding

Discussion in 'Plesk for Linux - 8.x and Older' started by ropox, Jan 26, 2009.

  1. ropox

    ropox New Pleskian

    22
    23%
    Joined:
    Dec 14, 2007
    Messages:
    5
    Likes Received:
    0
    Hello everyone

    I've been banging my head around this but cant figure out what the problem is..
    named service wont start and i know why. i followed the thread i found over here
    but i got stuck to the point where i get a bad base 64 encoding while loading named

    here is what my named.conf file looks like:
    options {
    directory "/var";
    dump-file "/var/named/data/cache_dump.db";
    statistics-file "/var/named/data/named_stats.txt";
    /*
    * 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; };
    };


    and my /etc/rndc.conf

    key "rndc-key" {
    algorithm hmac-md5;
    secret "CeMgS23y0oWE20nyv0x40Q==";
    };

    options {
    default-key "rndc-key";
    default-server 127.0.0.1;
    # default-port 953;
    };


    and my /etc/rndc.key

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


    doing a service named start gives these log messages

    Jan 27 00:45:11 myserver named[14215]: using 8 CPUs
    Jan 27 00:45:11 myserver named[14215]: loading configuration from '/etc/named.conf'
    Jan 27 00:45:11 myserver named[14215]: no IPv6 interfaces found
    Jan 27 00:45:11 myserver named[14215]: listening on IPv4 interface lo, 127.0.0.1#53
    Jan 27 00:45:11 myserver named[14215]: listening on IPv4 interface venet0:0, 00.205
    .30.78#53
    Jan 27 00:45:11 myserver named[14215]: listening on IPv4 interface venet0:1, 00.205
    .00.103#53
    Jan 27 00:45:11 myserver named[14215]: /etc/rndc.key:1: configuring key 'rndckey':
    bad base64 encoding
    Jan 27 00:45:11 myserver named[14215]: loading configuration: bad base64 encoding
    Jan 27 00:45:11 myserver named[14215]: exiting (due to fatal error)
    Jan 27 00:45:11 myserver named: named startup failed


    WHY IS THIS HAPPENING ??? I have the same key on both rndc.conf and rndc.key files

    this is so frustrating.... I don't have my mail server running because of this....
    Could anyone give me some advice ? would be much appreciated ...

    PS i have googled a lot before deciding to write this post....
     
    Last edited: Jan 26, 2009
  2. Amin Taheri

    Amin Taheri Golden Pleskian Plesk Certified Professional

    33
     
    Joined:
    Jul 5, 2007
    Messages:
    1,398
    Likes Received:
    1
    Location:
    Seattle Area
    I found this on google - did you try this?
    What do you get when you do rndc status?

    You may be able to just regenerate your rndc key since it appears corrupted, and on that note I found this
     
Loading...