Francis Lavoie
Francis Lavoie
You should raise this issue on the libdns repo for route53. I don't think this is a problem with `caddy-dynamicdns`. You can open an issue here: https://github.com/libdns/route53
> Because the functionality for the other libdns operations required by Caddy work just fine. `caddy-dynamicdns` does different operations. And it works fine with other DNS plugins such as CloudFlare...
I guess that might be related to the changes in https://github.com/libdns/libdns/issues/12 and https://github.com/libdns/libdns/pull/28.
> What I wanted was to specify IP version for each domain. I think that would make the config pretty complicated, and would be a breaking change in the config...
Sorry, my intent wasn't to be dismissive either, just wanted to clarify that this sort of change isn't necessarily "easy". For a change not to be breaking, only new config...
I'll work on implementing `update_only` after #16 is merged
I think https://github.com/caddyserver/caddy/pull/3990 should theoretically make this possible, but uh, it'll still be pretty awkward because it'll be configured via global options, if taking that route. Ultimately, I think this...
Thanks @RussellLuo! That's a good start. I agree it probably makes sense to have that support as a plugin outside of `caddy-l4` for now since there's still room for eventually...
> Nothing's stopping anyone from making a Caddyfile like that though! Actually, what is stopping it is that tons of the code for registering directives and global options are within...
Docker labels are out of scope for this plugin.