WARNING: key file (/etc/rndc.key) exists, but using default configuration

Status
Not open for further replies.

MarcoH64

Member
Oct 4, 2005
16
0
151
Thailand
cPanel Access Level
Root Administrator
Every time i do anything with DNS on an almost freshly installed server, i get the following warning in WHM:

Code:
Error reconfiguring bind on web1: WARNING: key file (/etc/rndc.key) exists, but using default configuration file (/etc/rndc.conf)
This happens when editing a DNS zone (without making any actual changes) or when adding a new cPanel account.
 

gnutoolbox

Member
Sep 25, 2011
23
0
51
cPanel Access Level
Root Administrator
Re: WARNING: key file (/etc/rndc.key) exists, but using default configurati

try /scripts/fixrndc and restart the nameserver (service named restart)
 
Last edited:

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,909
2,222
463
Re: WARNING: key file (/etc/rndc.key) exists, but using default configurati

Hello :)

It's possible this is related to an existing bug related to the use of CentOS 6.

Could you let us know which Operating System and version of cPanel is installed on this system?

Thank you.
 

MarcoH64

Member
Oct 4, 2005
16
0
151
Thailand
cPanel Access Level
Root Administrator
Re: WARNING: key file (/etc/rndc.key) exists, but using default configurati

Hello,

That sounds like it could be the case, sorry for not stating the OS and cPanel version in the OP.

O.S.: CentOS 6.0 64-bit
cPanel: 11.30.4.6
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,909
2,222
463
Re: WARNING: key file (/etc/rndc.key) exists, but using default configurati

Yes, this is a known bug associated with CentOS 6 and rndc. For reference, the internal case number is:

# 51794

That case is a backport, with the resolution scheduled to be included in cPanel version 11.30.5.

You can monitor our Change Log at:

cPanel Change Log

Please note the message is just a warning, and does not affect functionality. I am closing this thread at this time. If you continue to experience problems after the fix is published, feel free to use the following URL to submit a bug report:

Submit A Bug Report

Thank you.
 
Status
Not open for further replies.