rndc: connect failed: connection refused

Login to root SSH and run the following:

/scripts/fixndc

 

Or if you are like me and you could care less about scripts, you look in /etc/rndc.key find the

key { ...
.....
};

block, and copy it to your named.conf, and make sure the control section of named.conf says to use this key for localhost. And that the server section in rndc.key says to use this key for localhost.

I never have bothered to learn what all these scripts do, i just do everything by hand since that was how i grew up

 

Problem From named.conf
-----------------------------------wrong----------------
controls {
inet 127.0.0.1 allow { localhost; } keys { rndckey; };
};
----------------------------------wrong-----------------



--------------------------------correct------------------

controls {
inet 127.0.0.1 port 953
allow { 127.0.0.1; } keys { "rndc-key"; };
};
-----------------------------correct---------------------




{ rndckey; }; to { "rndc-key"; }; with actual your local IP and your port
you can find in rndc.conf not in rndc.key !

 

backup existing named.conf and rndc.conf, execute command "rndc-confgen". try using this new conf

 

We have a 7.3 server as our primary DNS and it uses the rndckey directive instead of the rndc-key our 9 and Enterprise servers use. Someone suggested that the secondaries be moved to match the primary of rndckey. Is this correct or should they all be rndc-key for Bind 9?

We plan on updating all servers to Enterprise, just takes time.