BIND 9.3.0: 'check-names response' refuses to ignore
RWYoung at verisign.com
Tue Oct 19 14:10:34 UTC 2004
That's strange because I have it in mine (Windows desktops were driving me nuts with our internal DNS) and I don't get them in the log anymore.
From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org] On Behalf Of Irwin Tillman
Sent: Tuesday, October 19, 2004 7:05 AM
To: bind-users at isc.org
Subject: BIND 9.3.0: 'check-names response' refuses to ignore
I'm running BIND 9.3.0 on Solaris 9.
The code indicates that the following behavior is the default:
check-names response ignore;
But named behaves as if the default for responses is 'warn', not 'ignore'.
E.g. it logs messages like:
in.named: resolver: notice: check-names warning union+city-nj.addresses.com/A/IN
in.named: resolver: notice: check-names warning shoprite.com/NS/IN
in.named: resolver: notice: check-names warning 126.96.36.199.in-addr.arpa/PTR/IN
Adding 'check-names response ignore;' to the global options does not appear to help.
Any ideas as to how to get check-names response to ignore?
More information about the bind-users