Isn't it time to upgrade?
On 18.04.13 08:35, Ben-Eliezer, Tal (ITS) wrote:
Yes, it is. In fact, adding these statements to the options clause is in
preparation for our migration to a later version.
It seems from my testing that while BIND 9.4 was very passive about these
type of records, and wo
onse";
Ok, I'm reading up on that now. Should I be able to suppress the logging using:
"check-names response ignore;" ?
Thanks
-Original Message-
Date: Wed, 17 Apr 2013 17:58:30 +0200
From: Matus UHLAR - fantomas
To: bind-users@lists.isc.org
Subject: Re: BIND 9.4.x an
On Apr 17, 2013, at 8:58 AM, Matus UHLAR - fantomas wrote:
> On 17.04.13 06:39, Ben-Eliezer, Tal (ITS) wrote:
>> default.log:12-Apr-2013 00:45:37.447 general: warning: zone
>> /IN: gc._msdcs./A: bad owner name (check-names)
>> default.log:12-Apr-2013 00:45:37.447 gene
On 17.04.13 06:39, Ben-Eliezer, Tal (ITS) wrote:
Subject: BIND 9.4.x and check-names
Isn't it time to upgrade?
I recently implemented a change in our DNS environment with the intention
of suppressing the log events related to AD-integrated zones, and their
Non-RFC compliant nature.
"Ben-Eliezer, Tal (ITS)" wrote:
Good Morning,
I recently implemented a change in our DNS environment with the intention of
suppressing the log events related to AD-integrated zones, and their Non-RFC
compliant nature.
In the global configuration I added the following statements:
check-names
Good Morning,
I recently implemented a change in our DNS environment with the intention of
suppressing the log events related to AD-integrated zones, and their Non-RFC
compliant nature.
In the global configuration I added the following statements:
check-names slave ignore;
check-names master i
6 matches
Mail list logo
