GoDaddy plugin doesn't work with Domain Protection enabled

[BearGFR]

To be clear, this is not an issue with your code or the godaddy plugin, but an issue with godaddy itself. I'm merely raising this as an issue for awareness.

The issue is, when working with a domain registered through godaddy (or using godaddy for DNS), if that domain has godaddy's "Domain Proctection" feature enabled, then their API for creating DNS records -does not work-. What happens, at least in the case of TXT records, is that the record will be created but the body/text portion of the record will be completely empty. Of course this causes the new-PAcertificate function to fail because the output TXT record in the godaddy DNS will not contain the needed validation key.

I proved this myself just moments ago. Yesterday I added domain protection to just one of my domains, then later discovered that new-PAcertificate was failing due to a blank _acme-challenge record. The very same code worked fine against another godaddy domain of mine that does not have protection enabled. I finally made the connection, and disabled protection on the one domain that had been failing, and now it works fine.

[rmbolger]

Hey @BearGFR, thanks for the heads up! I'll add a warning to the plugin guide.

[BearGFR]

Sure thing. I did also report the problem to ***@***.******@***.***>, but who knows if they’ll do anything about it.