On 01.10.20 17:46, Olivier wrote:
Here or there, you can read configuration files named like db.192.168.42
when holding data for a 192.168.42.0/24 network.
For networks with a /24 mask, simply striping ending 0/24 substring from
192.168.42.0/24 is enough.
But what about network with a different
> On 1. 10. 2020, at 17:27, Olivier wrote:
>
> 1. I'm hesitant to file a bug on Debian about this. As this both involves
> Bind9 and AppArmor, would you say it deserves to be implemented and
> documented in default Bind9 installation or that it is too specific for this ?
Speaking with my Deb
Hello,
Here or there, you can read configuration files named like db.192.168.42
when holding data for a 192.168.42.0/24 network.
For networks with a /24 mask, simply striping ending 0/24 substring from
192.168.42.0/24 is enough.
But what about network with a different prefix ?
1. How can you com
Hello,
Thank you all for replying !
Thanks to your suggestions, creating an /etc/bind/subdir directory, and
tweaking /etc/apparmor.d/usr.sbin.named allowed me to let ISC DHCP update
Bind9 entries.
1. I'm hesitant to file a bug on Debian about this. As this both involves
Bind9 and AppArmor, woul
My config took the following combination before it would work:
max-recursion-depth 20;
max-recursion-queries 275;
I'm running both IPv4 and IPv6.
Regards,
Bob
On Thu, Oct 1, 2020 at 2:37 AM Borja Marcos wrote:
>
>
> > On 30 Sep 2020, at 22:34, Mark Andrews wrote:
> >
> > No,
> On 1 Oct 2020, at 08:36, Mark Andrews wrote:
>> According to the documentation the default values for fetches-per-zone and
>> fetches-per-server are zero,
>> which means there is no limit.
>
> Sorry, shouldn’t answer when on a phone. See max-recursion-queries
Thanks, yes, I found it while
6 matches
Mail list logo
