Tatsuro Shibamura

@Apps-Limited Read the document. Also, I don't want comments that have nothing to do with this issue. https://github.com/shibayan/keyvault-acmebot/wiki#usage

Acmebot's DNS Provider implementation handles relative record names correctly, so I am not aware of any defects. It is left to the individual DNS Provider implementation.

It is a CustomDnsProvider-specific specification, not a bug in Acmebot's implementation; different DNS Providers require different information, so they pass neutral values.

I believe that the correctness of the DNS Provider can only be verified by running the actual DNS API. I don't see the value in testing code using a mock...

I will consider implementing it, but it is a low priority.

Now that I have a better understanding of CNAME support, I will start to consider supporting it when I have more time.

Error logs collected by Application Insights are required to identify the problem. Please share the logs of the relevant errors.

See this article. https://docs.microsoft.com/en-us/azure/azure-functions/analyze-telemetry-data

### Current Status #### Blocking issues - https://github.com/Azure/azure-sdk-for-net/issues/31701

The GratisDNS Provider is unmaintained and will be removed in Acmebot v4. Contributions are always welcome.