>From the DIFFERENCES file:
| 2.3 b-nonxdom - bind misses NXDOMAIN when no zone cut
|
| Bind8 refers to itself if it is asked for an authoritative answer in
| cases where there is no zone cut but other data.
|
| Analysis:
|
| A bind bug.
|
| Example:
|
| zone file:
| www.pool-effekt 86400 IN A 194.246.96.72
|
| bind8: 82 889 *- 0/1/0
| A? pool-effekt.de.;
| de. soa dns.denic.de. ops.denic.de. 2002031701 10800 7200 3600000 3600;
|
| NSD: 82 889 *- 0/1/0 NXDOMAIN
| A? pool-effekt.de.;
| de. soa dns.denic.de. ops.denic.de. 2002031701 10800 7200 3600000 3600;
I think it is consensus that returning NXDOMAIN in this case is a bug,
and not the other way round. Some versions of BIND 9 behave like nsd,
but recent ones should have been fixed to restore the BIND 8 behavior.
I think I've got a RFC quote somewhere, but it's likely hard to find.
8->