named-checkzone behavior change?

[Jack Tavares]

I see this was intentional.
2800.     [func]                    Reject zones which have NS records which refer to
                                                CNAMEs, DNAMEs or don't have address record (class IN
                                                only).  Reject UPDATEs which would cause the zone
                                                to fail the above checks if committed. [RT #20678]

From: Jack Tavares
Sent: Monday, May 10, 2010 12:54 PM
To: Jack Tavares; bind-users at lists.isc.org
Subject: RE: named-checkzone behavior change?

Correction:

I am calling named-checkzone not checkconf.
this:
named-checkconf -k ignore -n ignore -i none test.net. <zonefile>

should read
named-checkzone -k ignore -n ignore -i none test.net. <zonefile>

the rest of the email is correct

From: Jack Tavares
Sent: Monday, May 10, 2010 12:49 PM
To: bind-users at lists.isc.org
Subject: named-checkzone behavior change?

I have downloaded 9.7.0-P1 and I am running into something odd with named-checkzone
I have a simple zone with an NS record that has no A or AAAA record.

named-checkzone has flags to ignore this. and this same command (see below) worked in 9.6

but given this zone file
test.net. 500 IN SOA d88.test.net. hostmaster.d88.test.net. 2010051001 10800 3600 604800 86400
test.net. 500 IN NS d88.test.net.

gives

zone test.net/IN: NS 'd88.test.net' has no address records (A or AAAA)
zone test.net/IN: not loaded due to errors.

Is this a bug? or do I have a flag missing or incorrect?



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20100510/92dafa1e/attachment.html>