named options

[Darren Gibbs]

We keep getting named 811 errors as follows: owner name "nov_happy1.bsbvmt.com" IN (secondary) is invalid - proceeding anyway

Our theory is that it's because these server names have an underscore in them. Does anyone know a named option to ignore these errors and not report them in syslog?

[Armin Feller]

The workaround is simple. There is a statement which can be coded in /etc/named.boot for 4.X versions of BIND or /etc/named.conf in 8.X and higher versions of BIND.

check-names primary ignore
and/or
check-names secondary

The thing to do is look at each zone specified in /etc/named.boot or /etc/named.conf and make sure that each zone specified has a corresponding "loaded" message in /var/adm/syslog/syslog.log.

[Steve Steel]

Hi

As shown

Have "check-names primary ignore" at the
start of the /etc/named.boot file on the primary server.
This is because the hostname does not conform to RFC 952 as it contains an "_" (underscore) character.

Same for secondary

Regards

Steve Steel

Quote of the moment
-------------------
"We are drowning in information but starved for knowledge."
-- John Naisbitt

[Darren Gibbs]

I've tried both options in the BIND 8.1.2 named.conf file and neither one seems to work. I am bouncing the daemon with every change. Any other ideas?

[Kellogg Unix Team · Accepted solution]

Darren,

Are you using the correct syntax? Because syntax in 4.9.x and 8.x are different. Try the following in your named.conf file -

options {
check-names slave ignore;
};

HTH
...Manjeet

[kish_1]

I had simillar issue, changeing "_"on hostname solved (do not use _ on hostname), as Steve is already mentioned about the same.