Accidentally ran rndc-confgen on a working BIND box

Luis Navarro ln at lunadesign.net
Mon Nov 25 02:07:00 UTC 2024


Thanks for the quick response!

 

I ran “sudo rndc status” on the box in question and on a test VM that’s configured almost identically to the box in question.

 

Both had very similar output.  Here’s the output from the box in question:

 

version: BIND 9.18.28-0ubuntu0.22.04.1-Ubuntu (Extended Support Version) <id:>

running on localhost: Linux x86_64 5.15.0-124-generic #134-Ubuntu SMP Fri Sep 27 20:20:17 UTC 2024

boot time: Mon, 25 Nov 2024 01:16:08 GMT

last configured: Mon, 25 Nov 2024 01:16:08 GMT

configuration file: /etc/bind/named.conf

CPUs found: 4

worker threads: 4

UDP listeners per interface: 4

number of zones: 7 (0 automatic)

debug level: 0

xfers running: 0

xfers deferred: 0

soa queries in progress: 0

query logging is ON

recursive clients: 0/900/1000

tcp clients: 0/150

TCP high-water: 0

server is up and running

 

Does this mean the box is ok as is?

 

From: Eric <eric at digitalert.net> 



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 <mailto: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/76b8a5cb/attachment.htm>


More information about the bind-users mailing list