[bind10-dev] Last name used after $INCLUDE

[Michal 'vorner' Vaner]

Hello

There's an interesting case with master files. As jinmei pointed out in
https://bind10.isc.org/ticket/2427#comment:11, it is not clear what should be
considered the previous name after a $INCLUDE directive:

| foo.example.com. IN A 192.0.2.1
| $INCLUDE some_file ; which ends with "bar.example.com. IN A 192.0.2.2"
|      IN AAAA 2001:db8::1
|
| Which name should be used for the AAAA RR? RFC1035 doesn't seem to
| be clear on this point; BIND 9 uses foo.example.com; NSD uses
| bar.example.com. In my understanding, your current implementation
| behaves like NSD.

I adopted the bind9 approach (after seeing this comment, I must admit I didn't
think of that corner case at first) and added a warning whenever this is found.
But is there a rationale behind bind9's or NSD's behaviour?

Thanks

-- 
I've already told you more than I know.

Michal 'vorner' Vaner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <https://lists.isc.org/pipermail/bind10-dev/attachments/20121217/fe78945e/attachment.bin>