On Fri, 20 Jan 2017 07:38:32 -0700 LaMont Jones wrote:
>
> Can you provide a named.conf that reproduces the issue?
>
file named.conf:
=== 8< ===
include "/etc/rndc/rndc.key";
controls {
inet 1.1.1.1 port 953
allow {
2.2.2.2;
} keys { "rndc-key"; }
On Fri, 20 Jan 2017 07:38:32 -0700 LaMont Jones wrote:
>
> Can you provide a named.conf that reproduces the issue?
>
I've tried commenting out everything locally modified, leaving basically a
default config.
It seems the only thing needed to reproduce this issue is to run bind in a
chroot.
bind
On Fri, Jan 20, 2017 at 02:35:16PM +0100, Arturo Borrero Gonzalez wrote:
> I believe this is a serious bug, since it affects the most common way
> to deploy bind9 server which is in a chroot.
> In my opinion, we should probably not release stable stretch with
> bind9 in this state.
>
> This is wha
Control: severity -1 serious
Hi,
I believe this is a serious bug, since it affects the most common way
to deploy bind9 server which is in a chroot.
In my opinion, we should probably not release stable stretch with
bind9 in this state.
This is what I get in systemctl status:
ene 19 13:38:04 name
4 matches
Mail list logo