Open eloekset opened 2 years ago
You could always delegate the DNS to an Azure DNS zone and then use this bot with that. That's what I'm doing with Namecheap. Not trying to say this isn't a valid feature though, just suggesting a workaround in case you didn't know.
Thank’s! I didn’t think of that possibility.
I’ll try to implement a NamecheapProvider
and will send a PR if I get it up and running in my private release. If not, I’ll switch to Azure DNS. That option comes with additional costs, I assume?
It’s $0.50 a month per DNS Zone, so not too bad. It’s straightforward too. Here’s the guide I used. https://docs.microsoft.com/en-us/azure/dns/dns-delegate-domain-azure-dns
Is your feature request related to a problem? Please describe. I use Namecheap for most of my domains. Namecheap is currently not among the supported DNS providers.
Describe the solution you'd like Support for Namecheap gets added.
Describe alternatives you've considered Took a look at the custom provider configuration, but it seems to fail already at the ApiKeyHeaderName setting, because Namecheap requires API key in query string.
Additional context Documentation of Namecheap API:
I think the only issue with Namecheap API is that you have to whitelist IP addresses that can access the API, and you also need to specify which IP address you're calling the API from in the API call. This will be hard to do with Azure.