Bind 8.2.3, zone rejected due to CNAME error

[tmaestas at dnsconsultants.com]

	This is illegal.  8.2.3 will not serve a zone
	that it finds errors in, unlike earlier versions
	of BIND that would serve it non-authoritatively.
	Fix the errors in your zones.  Also, fix you
	"unattended updates" so that they do not put
	invalid data into your zones.

-Tim


On Mon, 26 Mar 2001 Peter.Pedersen at sas.dk wrote:

> 
> Hi,
> 
> The version 8.2.3 of bind reject the entire zone, when it find an error in a
> CNAME e.g.
> 
> server.foo.com.	IN A 172.1.1.200
> server.foo.com.	IN CNAME host.foo.com.
> 
> The behaviour seems to be the same for both "check-names warn/ignore"
> options, and the server does not answer any queries for this zone and does
> not allow any zone-transfer.
>  
> The previous version 8.2.2 pl 5 did also reject the zone, but the result was
> different, it continued to answer queries for the zone, but did not allow a
> zone-transfer.
> 
> Are the "No answer to queries" inteded, or is it a bug/feature?
> How can we avoid it?
> 
> We are running some unattended updates to the zone-files, which can cause in
> CNAME-errors, and would prefer the "old" behaviour, since it only affected
> the zone-transfer and not the queries.
> 
> Thanks in advance
> 
> Peter Pedersen
> Scandinavian IT Group 
> Senior Specialist
> ES&NM - Enterprise System & Network Management
> Tel. + 45 32 32 61 38
> Mob. + 45 20 89 09 10
> Fax. + 45 32 32 67 31
> www.scandinavianIT.com
> 
> 
>