Comment 15 for bug 1917099

I looked into this more today.

As I suspected, if you put child.parent.example.com. in a separate pool you are able to create the delegation NS record.

By splitting it into a separate pool you let Designate know that they are not in a direct parent/child relationship and the child doesn't fall under the zone of the parent zone.

This also makes sense for your child zones as if they are being distributed to alternate secondaries, wouldn't you want a different NS record list for those alternate servers? I wouldn't expect you would want to share the same ns_records pools.yaml setting across those two zones if they are being served by difference secondaries.