zone parse incomplete

[Kevin Darcy]

ali alkhalidi wrote:

>greetings all,
>I have:
>server1 primary master for x.y, and also configured as slave for z.x.y (both
>in named.conf and x.y.zone file as:
>z.x.y     in    ns       server2
>            in    ns       server1
>server2 primary master for z.x.y but does not contain server1 as an NS for
>z.x.y in the zone file
>
>when loading the zone file for x.y it loads only the first record, namely:
>z.x.y     in    ns       server2
>but not the second one.
>other than the distinction that server2 should list server1 as a secondary
>in the zone file, server1 should at least list server1 as is in the zone
>file for x.y, right?
>
Well, at a zone cut, there's a subtle distinction between what is 
*loaded*, and what is actually *visible* at the cut. Since server1 is 
authoritative for z.x.y, when you query it for the z.x.y NS records, 
it'll give you the NS records from the z.x.y zone, i.e. what it 
replicated from that master of that zone. The delegation records from 
x.y to z.x.y are *there*, in its database, but they are "hidden" by the 
other NS records, and not visible via an NS query. You could, however, 
see the delegation NS records in a zone transfer of x.y.

Perhaps you are used to the old BIND 8 behavior where named *combined* 
the NS records from the parent and the child (???). That was never 
correct, and BIND 9 finally fixed that behavior.

                                                                         
                                                            - Kevin