DNS notification based on TSIG is not supported

This is similar to https://bugs.launchpad.net/designate/+bug/1852902 , maybe you can create a common spec.

ok i will do the SPEC for this

just initial thought for the https://bugs.launchpad.net/designate/+bug/1852902
When the user add TSIG key to a zone and the backend is BIND, PDNS then using command line Nsupdate, and PDNS api (depend on dns server version) the tsig key will be added to backend plugin
A designate configuration can be added to enable/disable this feature and it will be disabled by default for backward compatibility

for the split view:

Solution 1.
I was working on this before https://review.opendev.org/#/c/693583/
which add the concept of internal/external view to the recordset so when an AXFR/also-notify happens for the recordset it will choose the right tsig-key, or response with the correct recordsets based on the tsig-key
for example if the recordset is marked external, external tsig-key is used for also-notify and this recordset will appear in the external view in AXFR if the external tsig-key is used

but before u said before u need more details about it (if this is ok i can provide more details)

Solution 2:
A new Type of zones is created called split-view when the user create a split-view zone designate will do the following
    * Create two zones in the backend
          Zone-internal
          Zone-external
    * Create two tsig-keys and attach them to the zone
          Internal-tsig key
          External-tsig key
    * In the backend plugin attach tsig-key to corresponding zone (internal/external)
    * AXFR/also-notify will be handled by the backend plugin

what do u think about each direction ( each one has cons/pros )

the idea with designate and split-view the user should know only one zone example.com. (not multiple internal / external zones)

am sending this to point me in the right direction so i can begin writing detailed SPEC

and i think this ticket is related too https://bugs.launchpad.net/designate/+bug/1877681

any update on this? :)

i added a spec for the second solution below the link
https://review.opendev.org/732450

Reviewed: https://review.opendev.org/732450
Committed: https://git.openstack.org/cgit/openstack/designate-specs/commit/?id=9dc089be2b6bdaa6d9cbbc8ccece2b310536c4d2
Submitter: Zuul
Branch: master

commit 9dc089be2b6bdaa6d9cbbc8ccece2b310536c4d2
Author: hamalq <email address hidden>
Date: Mon Jun 1 20:53:13 2020 +0000

    Adding a spec for implementing the split view feature in designate

    The spec include the details about the implementation of split_view
    Closes-Bug:1875939

    Change-Id: Ib646c3065d9cffa75e2763115a38ad718bfe2490

Related fix proposed to branch: master
Review: https://review.opendev.org/748285

Fix proposed to branch: master
Review: https://review.opendev.org/755379

Change abandoned by "Erik Olof Gunnar Andersson <email address hidden>" on branch: master
Review: https://review.opendev.org/c/openstack/designate/+/755379