Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

www/caddy - Multiple DNS providers for Dynamic DNS #3994

Closed
Stitch10925 opened this issue May 23, 2024 · 3 comments
Closed

www/caddy - Multiple DNS providers for Dynamic DNS #3994

Stitch10925 opened this issue May 23, 2024 · 3 comments

Comments

@Stitch10925
Copy link

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

Is your feature request related to a problem? Please describe.
I have multiple domains with Namecheap. Namecheap provides an automatically generated key per domain, which needs to be used to update the IP address of that domain. Since only one provider can be added, I am limited to dynamically updating a single domain since the key for the other domain is different.

Describe the solution you'd like
It would be nice if it was somehow possible to add multiple providers and to link them to a domain so that multiple domains can be dynamically updated (at least in case of Namecheap).

Describe alternatives you've considered
Adding another DynDns plugin to OpnSense is an option, but at the moment it does not contain the option to dynamically update Namecheap domains.

@Monviech
Copy link
Member

The way Namecheap handles it is interesting.

The problem is that the dynamic dns module doesn't support that. It can only add one dns provider with one api key. So the GUI doesn't allow anytjing different either.

https://github.com/mholt/caddy-dynamicdns

The dynamic DNS global block in the Caddyfile can only exist once with one API key.

You probably have to switch DNS providers to a better supported one.

@Monviech
Copy link
Member

Monviech commented May 24, 2024

mholt/caddy-dynamicdns#47

This won't be possible to implement in the plugin since the upstream dynamic dns implementation doesn't support it as of now.

This issue can be closed.

@francislavoie
Copy link

I'll just take the liberty of writing a more aggressive statement: Namecheap's API is hot garbage, you should move away ASAP to a DNS provider that doesn't suck as much. Viable options include Cloudflare and Porkbun.

@Stitch10925 Stitch10925 closed this as not planned Won't fix, can't repro, duplicate, stale May 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants