You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
https://docs.powerdns.com/authoritative/catalog.html#setting-up-a-producer-zone
does not mention that the SOA-EDIT of the zone should be NONE (either by setting it explicitly or having that value in default-soa-edit. I observed SOAs using the YYYYMMDDNN pattern when setting up a catalog zone while having default-soa-edit set to INCEPTION-EPOCH, rendering the catalog hash mechanism ineffective.
Alternatively, producer zones should use the NONE setting by making the code do the right thing
The text was updated successfully, but these errors were encountered:
I think documenting the interaction of SOA-EDIT with the automatic soa calculation is sufficient. I can imagine SOA-EDIT can be useful is setups with very few catalog zone updates to trigger periodic re-syncs.
In my config I have set default-soa-edit=INCEPTION-INCREMENT, and was adding a catalog zone following the docs.
This seems to lead to the SOA value not being updated when adding/removing a zone to the catalog. After changing the SOA-EDIT value to NONE for the catalog zone the value in the AXFR finally was set to the EPOCH as required, but of course I now have to manually force-update the catalog zone on the secondaries to make things work.
I think it makes sense to add a word to the docs that the SOA-EDIT value needs to be set to NONE.
https://docs.powerdns.com/authoritative/catalog.html#setting-up-a-producer-zone
does not mention that the
SOA-EDIT
of the zone should beNONE
(either by setting it explicitly or having that value indefault-soa-edit
. I observed SOAs using the YYYYMMDDNN pattern when setting up a catalog zone while havingdefault-soa-edit
set toINCEPTION-EPOCH
, rendering the catalog hash mechanism ineffective.Alternatively, producer zones should use the NONE setting by making the code do the right thing
The text was updated successfully, but these errors were encountered: