OK I fixed the root issue by introducing a forwarding zone for example.com to
get the resolution for ns{1,2,3}.example.com from internet nameservers:
zone "example.com" IN {
type forward;
forwarders { 1.1.1.1; 8.8.8.8; };
};
Now, the notification can start at all, but then the notifies
Additional difference between the old Bind 9.8.1 Host and the new Bind 9.11.3
Host is that the new (test) Host cannot (and shall not) reach the external DNS
servers that are in the SOA records of the DNS zones we host as "hidden
primary" and notify to the external bind hosts. (because it is
Please see my comments between the citates.
> Betreff: No "notify" category debug log entries anymore with Bind 9.11.3
>
> On old server with Ubuntu 12 and Bind 9.8.1
> I got the following "notify" category log entries as expected (domain names
> and IP addresses redacted):
>
> 27-Dec-2021
> On 20 Dec 2021, at 17:56, Reindl Harald wrote:
>
>
>
> Am 20.12.21 um 17:53 schrieb Petr Menšík:
>> sure I confused that. I read it wrong way and thought they are present
>> on *BSD but not on Fedora. I know some messages are removed in Fedora
>> builds. I apologize for a confusion. Nobody
Mik J via bind-users wrote:
> How can I check which variables are loaded in memory and considered as active.
As Ray said, usually it isn't ambiguous.
But there are a couple of semi-relevant tools that are worth knowing
about:
You can use `named-checkconf -p` to canonicalize your configuration
5 matches
Mail list logo
