search

NLnetLabs / draft-toorop-dnsop-dns-catalog-zones

Work on catalog zones
3 stars 11 forks source link

Behavior if a zone exists on a secondary already, then is added to a primary catalog zone #15

Closed isc-chuck closed 2 years ago

isc-chuck commented 3 years ago

Hello, all.

We need to check if the draft covers this behavior well.

Situation: BIND secondary auth is configured with a forward zone that is not on the primary, then that same zone is added to the primary catalog zone and transferred to the secondary, then secondary ends up with two copies of the zone config and behaves erratically.

What is the correct/expected/preferred behavior of this case? Generally: catalog zone data shouldn't clobber local config, but it might clobber local config in the case of forward zones, because of the nature of how DNS works.

wtoorop commented 2 years ago

This is "resolved" in Section 6.3 "Member zone name clash" in version -03 and the upcoming -04.