Skip to content

add TXTMulti capability to the namedotcom provider#299

Merged
tlimoncelli merged 3 commits intoStackExchange:masterfrom
pmoroney:namecom-txt-multi-for-real
Jan 11, 2018
Merged

add TXTMulti capability to the namedotcom provider#299
tlimoncelli merged 3 commits intoStackExchange:masterfrom
pmoroney:namecom-txt-multi-for-real

Conversation

@pmoroney
Copy link
Copy Markdown
Contributor

I believe we support the TXTMulti capability, these changes should allow it.
Let me know if the resulting DNS entries don't look right in production.

@pmoroney
Copy link
Copy Markdown
Contributor Author

Just realized I forgot to escape any quotes in the multitxt when sent to the API. I'll add that and an integration test when I get back to a computer.

@tlimoncelli tlimoncelli merged commit 91e2cf6 into StackExchange:master Jan 11, 2018
@pmoroney pmoroney deleted the namecom-txt-multi-for-real branch January 11, 2018 18:07
rblenkinsopp pushed a commit to rblenkinsopp/dnscontrol that referenced this pull request Aug 21, 2020
* add TXTMulti capability to the namedotcom provider
* run go generate
* escape multi txt records before sending to the API
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants