Joona Hoikkala
Joona Hoikkala
While the implementation might well be cursed, the feature is intentional. It is there to ensure the first priority and design goal of this project: security and limiting the impact...
I would still argue that the correct behavior would be to keep the limit and to use unique acme-dns credential set for every unique (sub)domain in the SAN list. The...
Unfortunately I haven't personally tested such scenario.
It’s actually intentional. On many configurations systemd resolved is listening at 127.0.1.53:53 which makes acme-dns unable to bind to 0.0.0.0:53 On Tue 1. Dec 2020 at 21.02, terminator14 wrote: >...
Yeah, you are right. It would probably serve the users better as far as the documentation goes. Do you want to create a PR to fix it or should I...
Hi, sorry it took a while to get around to reviewing this. The PR looks good, but I'd really like to see test cases included.
Thanks for the PR @jsoref , sorry it took so long to get around it. Is this still valid, and should it work as it is or does it need...
Ok, thanks!
Thanks for opening the issue! I certainly see the need for this feature. The medium term development plan I have is to replace the currently used SQLite database implementation with...
Hi! From your writeup it seems that you're missing the crucial NS record for the domain. The CNAME is not needed for acme-dns instance itself as it handles all that...