Marek Vavrusa authored Jan 19, 2016 and Grigorii Demidov committed Jan 20, 2016

there are broken resolution chains where a zone cut is advertised,
but it doesn't exist and the final NS answers from its parent's
zone cut, which is an attempt to escape bailiwick

example:

resolving A ab.cd.ef
NS ef responds:
 - ab.cd.ef NS X ; adverises ab.cd.ef zone cut
X responds:
 - A ab.cd.ef A 1.2.3.4
 - cd.ef NS X ; escapes previously advertised cut

on the other hand, it is important to fail early for referrals as
it signifies a lame answer

there are broken resolution chains where a zone cut is advertised,
but it doesn't exist and the final NS answers from its parent's
zone cut, which is an attempt to escape bailiwick

example:

resolving A ab.cd.ef
NS ef responds:
 - ab.cd.ef NS X ; adverises ab.cd.ef zone cut
X responds:
 - A ab.cd.ef A 1.2.3.4
 - cd.ef NS X ; escapes previously advertised cut

on the other hand, it is important to fail early for referrals as
it signifies a lame answer

this is broken by changes in libknot2/db api,
needs to be done differently later

the field length is platform-dependent

Grigorii Demidov authored Dec 30, 2015 and Marek Vavrusa committed Jan 10, 2016

lib: answer finalization was changed

this is not going to be backwards compatible change, but it will be the first tagged libknot release sufficient for resolver

thanks @darix!
fixes #21,#22

fixes #20

fixes #19

fixes #18