Haven't run into that error, myself.
Do you have the following in your /etc/named.conf file?
controls {
inet 127.0.0.1 allow {
localhost;
}
keys {
"key";
};
};
key "key" {
algorithm hmac-md5;
secret "<insert actual key, here";
};
The key name, "key" should actually match what's in rndc.conf, so if the
key name is actually "mykey" in rndc.conf, you need to make sure it's
called "mykey" in named.conf.
On Tue, 10 Sep 2002, Michael Tiernan wrote:
> On Monday 09 September 2002 20:01, Mike Burger said:
> > It's already generated...look in /etc/rndc.conf file.
>
> I realize that. I'm now assuming that this error:
> $ rndc -V status
> creating log channel
> enabling log channel
> create parser
> get key for server
> get config key list
> rndc: decode base64 secret: bad base64 encoding
>
> is a hint that there's something wrong with the key in some form or fashion.
> So, I figured, start with learning how the key is generated locally. Then,
> I'd probably get a better lead as to what's wrong.
>
>
>
>
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list
