Accidentally ran rndc-confgen on a working BIND box

[Eric]

Trying using rndc to see if it's broke.

rndc status


You may need to add a path to the rndc binary if it's not in your $PATH env vars. Or maybe -c to the location of your rndc config.

In your named.conf you should have a rndc statement with the key name and value.

You can recreate your rndc config / key with that if needed.








Nov 24, 2024 6:36:57 PM Luis Navarro <ln at lunadesign.net>:

> I've been running BIND on Ubuntu 22.04 for over a year and it has been running perfectly as my primary DNS server.  I’m currently using BIND 9.18.28.
>  
> 
> I'm currently setting up BIND on another box (as a secondary DNS server) and accidentally just ran "sudo rndc-confgen -a" on the first box.  From what I can tell, running this command overwrote the previously installed "/etc/bind/rndc.key" file with a new one. 
>  
> 
> I'm vaguely familiar with rndc but don't think I've ever used it directly.  It is possible the BIND tools I typically use call it.  Anyway, the first box **seems** to still be working normally.
>  
> 
> *Questions:*  Did I break anything by running "rndc-confgen"?  Is there anything else I need to do on the first box to move forward with the new key file?  Or should I restore the key file from a backup?
>  
> 
> Thanks in advance!
> Luis
>  
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20241124/16090876/attachment.htm>