My bad. I spotted that afterwards.
On Thu, 28 Nov 2024 at 13:48, Anand Buddhdev wrote:
> On Tue, 26 Nov 2024 at 09:40, Greg Choules via bind-users <
> bind-users@lists.isc.org> wrote:
>
> Hi Greg,
>
> Running "named-checkconf -p" will print your entire named configuration,
>> following any inclu
On Tue, 26 Nov 2024 at 09:40, Greg Choules via bind-users <
bind-users@lists.isc.org> wrote:
Hi Greg,
Running "named-checkconf -p" will print your entire named configuration,
> following any include files. There *must* be a "controls" section in there
> or rndc could not work, since, from the ARM
Hi Luis.
Running "named-checkconf -p" will print your entire named configuration,
following any include files. There *must* be a "controls" section in there
or rndc could not work, since, from the ARM:
> all communication with the server is authenticated with digital
signatures...
I encourage you t
Thanks Greg!
I can confirm that running “rndc-confgen -a” replaced the previously created
"/etc/bind/rndc.key" file with a new one. There are no other files named
“rndc.key” on the box in question.
None of my conf files have a “controls” block in them. Is this bad? FWIW, I
don’t think
>From the ARM, when "rndc-confgen -a" is run::
> This option sets automatic rndc configuration, which creates a file
rndc.key in /etc (or a different sysconfdir specified when BIND was built)
that is read by both rndc and named on startup. The rndc.key file defines a
default command channel and auth
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 (Extende
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 co
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
8 matches
Mail list logo
