-
Notifications
You must be signed in to change notification settings - Fork 46
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
Fix should_content not correctly matching pdnsutil output #171
Conversation
This fixes two bugs when comparing zone contents to pdnsutil output, which triggers the continual re-import of managed zones: - an extraneous `\n` after `$ORIGIN .` which causes `\n\n` to be added to the resultant zone; - `rname` values being included in a case-sensitive manner, when records are always returned as downcase.
Okay now I can't trigger the bug with the old code, so something else has changed. |
Reopening this because a) the |
With no changes to zone, but uppercase record resources present: existing code:
changed code:
|
You know the more I think about this, the more I don't like this solution anyway. I'm gonna close it for now. |
This fixes two bugs when comparing zone contents to pdnsutil output, which triggers the continual re-import of managed zones:
\n
after$ORIGIN .
which causes\n\n
to be added to the resultant zone after record sort;rname
values being included in a case-sensitive manner, when records are always returned as downcase, which means that uppercase characters inrname
parameters cause zones to always be re-imported.Changing the relevant lines in
should_content
ensures that affected zones are only re-imported when records actually differ.No test changes are included as
powerdns_zone
contents do not currently have any tests running against them.