Add an option to allow AXFR of zones with a different (higher/lower) serial. #5169
Conversation
This file contains 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
Habbie
approved these changes
Mar 17, 2017
Habbie
added a commit
that referenced
this pull request
Mar 17, 2017
Backport: Add an option to allow AXFR of zones with a different (higher/lower) serial #5169
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Short description
Atm the AXFR of a zone stops if the serial is moving backwards and signatures start to expire. This is a very common problem in setups where the nameserver is secondary for many customers. Not everyone is a dns expert ;)
With this option it is possible to tell pdns to axfr the zone if the serial on the slave is different (higher/lower) from the one on the master.
Checklist
I have: