Replies: 4 comments
-
Ok - I've moved forward a little bit by adding |
Beta Was this translation helpful? Give feedback.
-
Those are the arguments I use in my for my script as an example. Don't use EasyDNS though. --dnsCreateScriptArguments "create {Identifier} {RecordName} {ZoneName} {NodeName} '{Token}'" |
Beta Was this translation helpful? Give feedback.
-
When I use the EasyDNS script through the step-by-step process the script parameter input is setup like this: create {RecordName} {Token} u123x4567y89z10.12345678 api123x4567y89z10.12345678 Using @CastaS comments above I would add your EasyDNS info after {Token} in a similar format as I have above. |
Beta Was this translation helpful? Give feedback.
-
In case anyone finds this while working with this script, mine was failing in powershell 5.1.14, but works in powershell 5.1.17 |
Beta Was this translation helpful? Give feedback.
-
Can someone please provide an example command-line usage for the EasyDNS validation plugin? How are the token and key values that are obtained from EasyDNS to be specified on the command line? Let's assume that my key is "api123x4567y89z10.12345678" and my token is "u123x4567y89z10.12345678".
wacs --test --verbose --accepttos --emailaddress <myemail@mydomain.com> --source manual --friendlyname "<My Friendly Name>" --commonname "<hostname.mydomain.com>" --host "<san.mydomain.com>" --store pemfiles --pemfilespath "<C:\Temp\MyPEMfiles>" --validationmode dns-01 --validation script --dnsscript "C:\ProgramData\chocolatey\lib\win-acme\tools\Scripts\EasyDNS.ps1"
I have tried using --EDKey api123x4567y89z10.12345678 and --EDToken u123x4567y89z10.12345678, and I have tried using --eab-key and --eab-key-identifier but neither have worked.
Beta Was this translation helpful? Give feedback.
All reactions