One of the things you may want to look into, is the notions of "acl" and
"masters". These are sections in named.conf that you can give names, that can
be referenced elsewhere. Below is one such config I have in my own systems
(with IP addresses partially redacted):
// Access Control Lists
// So
On Friday, January 31, 2025 10:03:06 PM CET Karol Nowicki via bind-users
wrote:
> Hi Everyone
> With design where one ISC Bind DNS server is a master for domain
> example1.com while in same time acts like as Slave for another one lets say
> example2.com do we breaks any ISC recomendations or good
Am 31.01.2025 um 21:03:06 Uhr schrieb Karol Nowicki via bind-users:
> With design where one ISC Bind DNS server is a master for domain
> example1.com while in same time acts like as Slave for another one
> lets say example2.com do we breaks any ISC recomendations or good
> practice ?
Such a conf
Hi Everyone
With design where one ISC Bind DNS server is a master for domain example1.com
while in same time acts like as Slave for another one lets say example2.com do
we breaks any ISC recomendations or good practice ?
Wysłane z Yahoo Mail do iPhone
--
Visit https://lists.isc.org/mailman/l
> On 31. 1. 2025, at 15:17, Ted Mittelstaedt wrote:
>
>>
>> zones.rfc1918 configuration files are going to be removed in favor of
>> empty-zones yes; (which is default)
>
> Just curious what the reason for removing the 1918 zone files is?
It is on the very same line you just quoted:
https:
On 31. 01. 25 15:17, Ted Mittelstaedt wrote:
On 1/27/2025 4:17 AM, Ondřej Surý wrote:
Hi,
In preparation for Debian trixie, following changes will be made to
the packages (as they are built from the same source):
zones.rfc1918 configuration files are going to be removed in favor
of emp
On 1/27/2025 4:17 AM, Ondřej Surý wrote:
Hi,
In preparation for Debian trixie, following changes will be made to the
packages (as they are built from the same source):
zones.rfc1918 configuration files are going to be removed in favor of
empty-zones yes; (which is default)
Just curiou
Hi Support Info,
that’s quite unusual name!
The BIND 9 packages in Debian have been properly updated:
https://tracker.debian.org/pkg/bind9
Whatever you are seeing is your local problem.
Ondrej
--
Ondřej Surý — ISC (He/Him)
My working hours and your working hours may be different. Please do no
Hello,
Following the CVE cve-2024-11187 and cve-2024-12705 concerning Bind9 I have two
debian servers whose repository cannot find the update:
apt-cache policy bind9
bind9:
Installed: 1:9.18.28-1~deb12u2
Candidate: 1:9.18.28-1~deb12u2
To patch to 9.18.33 Extended Support (ES), what do you
9 matches
Mail list logo
