check-names error
Barry Margolin
barmar at alum.mit.edu
Tue Jun 22 01:06:00 UTC 2004
In article <cb7vae$fsj$1 at sf1.isc.org>,
"Mathew Thomas" <mathew.thomas at rmit.edu.au> wrote:
> Hi
>
> I am in the process of upgrading all our DNS servers and I believe it is safe
> to use Bind 9.3.0rc1 in production
> servers. Currently we are running 9.2.3
>
> Is underscore supported in the new version? I am getting following warning:
No, underscores are not valid in hostnames. This check has been around
since BIND 8.
Your subject line mentions "check-names error". I don't see any errors
in your log excerpt, just warnings. Of course, if you *want* errors,
you can simply change the check-names option from "warn" to "error".
>
> Jun 22 09:51:34 its-du-ns3 named[25216]: [ID 866145 daemon.warning] zone
> gm.rmit.edu.au/IN:
> sm_hp_8550.gm.rmit.edu.au/A: bad owner name (check-names)
> Jun 22 09:51:34 its-du-ns3 named[25216]: [ID 866145 daemon.warning] zone
> gm.rmit.edu.au/IN:
> sm_oce_9300.gm.rmit.edu.au/A: bad owner name (check-names)
> Jun 22 09:51:34 its-du-ns3 named[25216]: [ID 866145 daemon.warning] zone
> 173.170.131.in-addr.arpa/IN:
> 35.173.170.131.in-addr.arpa/PTR: adc_53_2_HPLj2200.adc.rmit.edu.au: bad name
> (check-names)
>
> Thanks
> Mathew
--
Barry Margolin, barmar at alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***
More information about the bind-users
mailing list