Support using BIND as a secondary nameserver.#444
Merged
Conversation
… a Cascade primary due to lacking AA flag in query responses, i.e. the SOA query from secondary to primary following a NOTIFY from Cascade to secondary.
bal-e
approved these changes
Feb 2, 2026
bal-e
approved these changes
Feb 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See #435 for the original bug report that this PR works around.
In manual testing with BIND 9.18.44 this resolves the issue described in #435 concerning failure to transfer the signed zone to BIND from Cascade.
As an automated test may take some time to develop and this is a blocking issue for users of BIND as a secondary I have not attempted to include an integration test in this PR, but believe we should develop such a test to prevent this and similar issues in future.
Note that this issue may not be expected because NLnetLabs/domain#400 resolved this problem in
domain. However, to work around another issue I earlier modified Cascade to useLightWeightZoneinstead ofZoneApexand only the latter contains the fix from #400.