dns_curanet API changed #6595
Description
We are using the dns_curanet plugin for some of our domains to manage wildcard certificates and they seem to have recently changed how the v1 API works so that it is now behaving similar to the new v2 API.
This means that if we make an API call with _acme-challenge.example.com in the URL during the process of getting a wildcard domain for *.example.com, then it fails with status code 400 and the error message of Domain '_acme-challenge.example.com' is not valid
If we however alter the API call to use example.com instead of _acme-challenge.example.com, then it does work
The fix would be fairly simple if it was just to to stripe of out the _acme-challenge part of the domain in the request, but the flow would still be broken for subdomains such as mysite.example.com as it is not the name of the DNS Zone.
So the fix would most likely be to fx. identify the actual top-level domain name