We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
First of all, thanks for your work on this! I've run into what seems to be a bug, but it very well could be user error.
I'm trying to set a TXT record using something similar to the following:
namecheap domains dns --domainname=domain.com --hostname=@ --recordtype=TXT --address="v=spf1 include:mailserver.com" --ttl=1800
But I'm getting an error saying: Error: expected element type <ApiResponse> but have <HTML>
Error: expected element type <ApiResponse> but have <HTML>
When I remove all spaces from the address argument, the command goes through. Is this a bug?
The text was updated successfully, but these errors were encountered:
@arharp Thanks for reporting this! I appreciate it.
I can confirm this is a bug. I will create a fix and do a release as soon as I can.
I am assuming you added the correct command in your example. Should be namecheap domains dns sethosts ...
namecheap domains dns sethosts ...
Sorry, something went wrong.
#1 - Add string QueryEscape
2c4c251
Can you try with the latest version @arharp ? v0.0.7
v0.0.7
@jsgv That fixed it. Thanks for the quick reply!
jsgv
No branches or pull requests
First of all, thanks for your work on this! I've run into what seems to be a bug, but it very well could be user error.
I'm trying to set a TXT record using something similar to the following:
namecheap domains dns --domainname=domain.com --hostname=@ --recordtype=TXT --address="v=spf1 include:mailserver.com" --ttl=1800
But I'm getting an error saying:
Error: expected element type <ApiResponse> but have <HTML>
When I remove all spaces from the address argument, the command goes through. Is this a bug?
The text was updated successfully, but these errors were encountered: