SUMMARY: problem with new bind 4.9.7

From: David W. Blaine (
Date: Mon Oct 18 1999 - 07:30:55 CDT

Hi Sun-managers:

I had one good response and several snide ones (something I didn't really care
to hear considering my plight at the moment!) I realized in my tense rush I
forgot to put in the OS and version info on my original post (my fault). But to
explain to the flamers, I posted this question on BOTH this list (just in case
it was a Solaris issue) and the DNS ones I know of. I was determined to cover
ALL the bases (like any good sys admin posed with a problem). So for those
narrow-minded, puffed-up individuals, I suggest you get off your podium and shut

Anyway, here is the lone reponder (Thanks Tim!) whose suggestion works while I
clean up my hosts table:

X-Lotus-FromDomain: EES
From: "Timothy Lindgren" <>
To: "David W. Blaine" <>
Date: Thu, 14 Oct 1999 18:12:15 -0500
Subject: Re: problem with new bind 4.9.7
Mime-Version: 1.0
Content-Disposition: inline

The quickest way is to CNAME the underscored hostname to valid addresses.

my-sunserver IN A
my_sunserver IN CNAME my-sunserver

When Bind does syntax checking, it only checks address "A" records, and
assumes the rest are authoritative to these.


------------- Begin Forwarded Message -------------

Date: Thu, 14 Oct 1999 15:12:47 -0400 (EDT)
From: "David W. Blaine" <>
Subject: problem with new bind 4.9.7
MIME-Version: 1.0
Content-MD5: 9YOGMhngLmUw7MiWCl1QKQ==

Hi Sun-managers:

I have an immediate problem. I loaded new bind 4.9.7 on my primary DNS server
knowing my hosts have underscores in them. Because of this, I added "check-names
primary ignore" to ignore these issues. My problem is it seems to be ignoring
the option not the name checking, because it is rejecting zones in which these
malformed hostnames fall. Could someone tell me a fix or workaround???

David Blaine (
Computer Systems Engineer
Phone: 810-825-7650

------------- End Forwarded Message -------------

This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:13:29 CDT