Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

auth: catalog zone producer docs do not mention SOA-EDIT should be NONE #14752

Open
omoerbeek opened this issue Oct 7, 2024 · 3 comments
Open

Comments

@omoerbeek
Copy link
Member

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

@omoerbeek omoerbeek added the auth label Oct 7, 2024
@Habbie Habbie added this to the auth-5 milestone Oct 7, 2024
@Habbie
Copy link
Member

Habbie commented Oct 7, 2024

@mind04 do you have opinions on this?

@mind04
Copy link
Contributor

mind04 commented Oct 7, 2024

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.

@mutax
Copy link

mutax commented Nov 7, 2024

I just ran into the same problem.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants