Copy the content from idrsa.pub (the SSH public key) to the previously created authorizedkeys file on the remote CentOS server by typing the command: scp /.ssh/idrsa.pub username@remotehost:/.ssh/authorizedkeysWith this, the public key has been safely stored on the remote account.
So I have an /etc/rndc.conf which has both the key and some other options in it (specifically a default-server pointing at a different IP address than 127.0.0.1). Use the chmod command to change the file permission: chmod 700 /.ssh && chmod 600 /.ssh/authorizedkeyschmod 700 makes the file executable, while chmod 600 allows the user to read and write the file.4. Now, open a new terminal session, on the local computer.5.
The named service is configured using the controls statement in the /etc/named.conf configuration file as described in Section 17.2.1.2, “Other Statement Types”.Unless this statement is present, only the connections from the loopback address (that is, 127.0.0.1) will be allowed, and the key located in /etc/rndc.key will be used. $ sudo service named reload rndc: neither /usr/local/etc/rndc.conf nor /usr/local/etc/rndc.key was found It took about 15 minutes of searching and reading to figure out my solution. Random cd key generator online. Vmware esxi 5.5 license key generator. Creating the key. I generated a key: # rndc-confgen -r /dev/urandom /usr/local/etc/rndc.conf That file looked something like this.
My problem is that the bind service will always go and create /etc/rndc.key regardless of whether there is an rndc.conf in place. This then generates a warning everytime I invoke an rndc command ..
# rndc reload