NAMECHEAP: fix support for url etc records #3538
Merged
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.
Resolves #3522
The custom record types URL, URL301, and FRAME can be created by the current version of dnscontrol but they cannot be read by subsequent calls.
It looks like the previous iteration of how things work defaulted to
record.SetTarget
whereas the current way relies onrecord.PopulateFromString
which does not have support for the custom record types.This small change appears to do the trick to resolve the problem, the type specified from the users config file makes it way to the commands to create the records no problem.
I am not sure how to write tests for this since it would be namecheap specific? It looks like vultr also supports the records but I do not have a vultr account to confirm if it currently works or not.
P.S. I edited the file in github, not sure why it is showing as unverified by maybe thats just github being silly.
P.P.S. now showing as verified, github silliness confirmed