: BIND 9.4.x and check-names
Barry S. Finkel
bsfinkel at att.net
Wed Apr 17 14:06:31 UTC 2013
"Ben-Eliezer, Tal (ITS)"<Tal.Ben-Eliezer at its.ny.gov> 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 slave ignore;
> check-names master ignore;
>
> Flushed & reloaded.
>
> However, I still see these entries appear in the logs. Could someone please chime in and let me know if my expectation or implementation was incorrect? Many thanks!!
>
> 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 general: warning: zone ****************/IN: gc._msdcs.************/A: bad owner name (check-names)
>
> Best Regards,
>
> Tal Ben-Eliezer
I would place those in each zone definition, rather than a global
config. You want to be alerted if a non-AD zone has a name
issue. Without more information, I cannot tell right now why those
directives did not work.
--Barry Finkel
More information about the bind-users
mailing list