This post is for information only.
Please don't alter my account(s) based on this thread.
On both my VPS accounts I had a problem whereby the designated hostname wouldn't 'take' properly. Symptoms were that I would get an email:
[ipcheck] Problems with dns setup, and a WHM pop-up stating that there was no dns zone 'A entry' for the hostname. In addition, I would get various system emails being bounced back, trying to email
root@vpsXXX.eukhost.com.
On saving the edited dns zone for the hostname, I saw this error:
Error reloading bind on server: rndc: connect failed: connection refused
It appears that this is a known issue with some WHM installations, so I thought I'd post a possible solution here for others:
-----------------------------------------
RNDC Fix #1:
Login to your server through SSH
Type:
cd /scripts
Type:
./updatenow
Type:
./fixndc
The above error will fix certain aspects of the RNDC Error, and sometimes fix all the problems. However during certain installations the problem will still exist, this is where RND Error Fix #2 comes in...
RNDC Fix #2:
Login to your server through SSH.
Type:
pico /etc/rndc.conf
Search for "rndc-key" and replace it with "rndckey"
CTRL-W is how to search in PICO.
CTRL-X Y to save and exit
Type:
pico /etc/named.conf
Search for "rndc-key" and replace it with "rndckey"
CTRL-W is how to search in PICO.
CTRL-X Y to save and exit
After that type:
/scripts/fixnamed
After that type:
/scripts/fixndc
If step #5 still produced an error type:
/scripts/fixndc
There should be no error now.
Now we will restart named (BIND)
Type: service named restart
If you get an error simply restart again.
Type: service named restart
-------------------------
After using fix #1, on editing the hostname dns zone file, I now see this message:
Bind reloading on HOSTNAME using rndc zone: [HOSTNAME.DOMAIN.com]
Reconfiguring Local Mail: This server will serve as the primary mail exchanger for HOSTNAME.DOMAIN.com's mail.