You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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?
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.
The text was updated successfully, but these errors were encountered: