fix: SetRecords replaces rrset values instead of appending#17
Open
zazabe wants to merge 1 commit into
Open
Conversation
Update README to reflect new behavior of AppendRecords and SetRecords.
Author
|
Works with caddy-dynamicdns, not sure about potential side effects for libdns/gandi usages in other caddy modules. |
Author
|
could fix #6 |
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
1 participant
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.
Split LiveDNS update logic:
SetRecordsnow PUTs a single-value rrset (fixes duplicate A records when an IP changes, e.g. with caddy-dynamicdns).AppendRecordsstill merges into an existing rrset.Adds table-driven mock API tests for set vs append (
www,@, new rrset, duplicate value).related to caddy-dns/gandi#15