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.

named-checkconf -k ignore -n ignore -i none test.net. <zonefile>
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?



Relevant Pages

  • Re: Using an MX record from a different domain
    ... This is fine so long as the "out of zone" MX record is valid, but named-checkzone wants you to know that it can't verify for sure. ... It might make sense to lower the TTL test, verify, then restore the TTL once the change has been blessed. ...
    (comp.protocols.dns.bind)
  • Re: Delegation question
    ... test your zone with named-checkzone. ... a delegation, the A record for the same name is probably a mistake). ... Actually I just found what caused it not to work; I have forwarders ...
    (comp.protocols.dns.bind)
  • RE: named-checkzone behavior change?
    ... I am calling named-checkzone not checkconf. ... Subject: named-checkzone behavior change? ... but given this zone file ... or do I have a flag missing or incorrect? ...
    (comp.protocols.dns.bind)
  • Re: bind 9.7.2-4.P3 in f14 not working with previous reverse, lookup zone file
    ... can't get bind to accept a zone file that worked with fc12 bind. ... satisfied named-checkzone but service named start still failed. ...
    (Fedora)
  • Re: 9.6.1-P1 zone parser false errors
    ... $ named-checkzone abcxyz.com abcxyz.com-hosts ... Of course, the l.google.com zone is different depending on where you are in the world, so it's conceivable that these values are different where you are than where I am. ... current BIND: ... abcxyz.com/MX 'alt1.aspmx.l.google.com' is a CNAME 'mail-bw0-f39.google.com' ...
    (comp.protocols.dns.bind)